iPhone -- FA-18 Marine Aviator

Announce new projects or updates of Irrlicht Engine related tools, games, and applications.
Also check the Wiki
Post Reply
digijohnny
Posts: 63
Joined: Sat Sep 12, 2009 6:08 pm
Contact:

iPhone -- FA-18 Marine Aviator

Post by digijohnny »

FA-18 Marine Aviator

Carrier Qualification Trainer
for the iPhone
IPad HD RELEASE THIS WEEKEND


http://www.digijohnny.com/MAF18CQ/




Unique 3D cockpit:
3 real Multi function Displays
3D instruments panel
3D cockpit Buttons
real transparent hud
multi function air/ground radar
target/navigation computer
full weapon load
1 fully animated FA-18 Hornet
1 aircraft carrier
1 LSO
ILS,IFOLS,AOA indicators everything you need to survive a con tolled collision with a boat!
1,2 wingman (bot or network buddy or both) replay over network.


RELEASE DATE 8/26/11
Image
Last edited by digijohnny on Thu Sep 01, 2011 7:17 pm, edited 3 times in total.
kine
Posts: 18
Joined: Tue Mar 23, 2010 9:40 am

Post by kine »

Very nice! !:-)
cobra
Posts: 371
Joined: Fri Jan 23, 2009 2:56 am
Location: United States
Contact:

Post by cobra »

Excellent work!
Josiah Hartzell
Image
polylux
Posts: 267
Joined: Thu Aug 27, 2009 12:39 pm
Location: EU

Post by polylux »

Whoa, that's some serious work! I'd love to play that on a non-iPhone device! :)
beer->setMotivationCallback(this);
digijohnny
Posts: 63
Joined: Sat Sep 12, 2009 6:08 pm
Contact:

Re: iPhone -- FA-18 Marine Aviator

Post by digijohnny »

many delays experienced with OSX 10.5->10.67 updates Xcode Updates Complete rebuild for universal ios3->4.2
and ipad version

Ipod and Ipad HD version submitted fri 19 waiting reviews
expected release sept. 2011

see homepage for current screenshots
digijohnny
Posts: 63
Joined: Sat Sep 12, 2009 6:08 pm
Contact:

Re: iPhone -- FA-18 Marine Aviator

Post by digijohnny »

Last edited by digijohnny on Fri Aug 26, 2011 5:36 pm, edited 1 time in total.
JamesMoon
Posts: 6
Joined: Fri Aug 26, 2011 4:23 am

Re: iPhone -- FA-18 Marine Aviator

Post by JamesMoon »

Looks Great..

I am starting a new project for iPad..

But, I am new to Irrlicht and 3d Engine..

Would you show us to start the job in Xcode with new Irrlicht project??

I mean.. a simple document?.. or Wiki?

Thanks..
digijohnny
Posts: 63
Joined: Sat Sep 12, 2009 6:08 pm
Contact:

Re: iPhone -- FA-18 Marine Aviator

Post by digijohnny »

I love to help, I've been programming for 31 years , so I'm not sure of you definition of simple, but I'm about to start a new 3dGUI project for this app and I'll be posting complete projects as example
JamesMoon
Posts: 6
Joined: Fri Aug 26, 2011 4:23 am

Re: iPhone -- FA-18 Marine Aviator

Post by JamesMoon »

digijohnny wrote:I love to help, I've been programming for 31 years , so I'm not sure of you definition of simple, but I'm about to start a new 3dGUI project for this app and I'll be posting complete projects as example
Thank you 'digijohnny'. I will follow your post. It would be great help.

About the 'simple'.. I reconsider it. It's not 'simple' rather 'detailed'..

For example:
If you use different version of Xcode, the route of setting would be different.

This kind of minor differences make huge waste of time.

I hope you develope in "Osx Lion and Xcode4 and the recent stable Irrlicht version"

I have 3 years of C++ programming experience. But, I don't want to study Cmake, or other tools.

But, if they are necessary, I should learn, of course. I just don't know what to learn.

I will wait your post. How about to make a new tutorial in the Wiki?..

Best regards
James
digijohnny
Posts: 63
Joined: Sat Sep 12, 2009 6:08 pm
Contact:

Re: iPhone -- FA-18 Marine Aviator

Post by digijohnny »

as soon as the initial flow of support for the app slows. im going to write up a post on the basic, but very obscure, thing i learned about xcode compare to command line or even MSC, honestly, the very last 2 things i learned on xcode (just 2 days ago) was how to change the name of the executable for sure, without kill you code sign, and just how many places you need to change the version number string when building you first update, i have been runnung with a hacked version of fuzzyspoons template since day one.
if you got some basic questions like that let me know
fmx

Re: iPhone -- FA-18 Marine Aviator

Post by fmx »

The usual way to change the name of the "executable" is just to give it a different name for the "bundle display name" in the info.plist file, or were you talking about changing the project name?
You should use the latest version of xcode wherever possible, I dont know much about fuzzyspoons template but I'd guess that it was based on a very old xcode project version.
digijohnny
Posts: 63
Joined: Sat Sep 12, 2009 6:08 pm
Contact:

Re: iPhone -- FA-18 Marine Aviator

Post by digijohnny »

more like, where $(PRODUCT_NAME) and $(EXECUTABLE_NAME) in the target info, because you only get 1 info.plist between two apps(ipod - ipad), this could have been a scew up when the project was conveted/update for xcode3.3 , i still have to manually change the bundle identifier for each separate build maf18cq to maf18cqhd
this means if you leave the $(Prod...) and $(EXECU....) in the plist you can change them in the target, then put them were ever you need them generically , basically
put the variable in the info.plist,
set he variable in the target info,so all targets use the same info.plist
i just need one for my bundle id now, but this is my second xcode app, and first to thread to ipad. and i learned all this last night

yeah, that ancient template from back in post 2 of the ogles thread, like two years ago. i was running 2.2.1on an 2gen ipod.
and with irrlicht i still am and pretty heavy.... TRY THAT UNITY!!!

iphone 0.99 cent sale 24 hrs only one day this weekend. then 7.99,now 5.99
ipad debuts at 1.99 then up to 9.99
digijohnny
Posts: 63
Joined: Sat Sep 12, 2009 6:08 pm
Contact:

Re: iPhone -- FA-18 Marine Aviator

Post by digijohnny »

turns out the info.plist file was tagged to be included in the target build, caused for cyclic redundancy thing
right clicked on info.plist removed from all targets
in the long run i just made separate project files for each build, using the same source files
much less confusing this way, especially when archiving builds for submission
Post Reply