Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[MichaelZ]

Yeah, me again...
       I've had some luck so far adding extra planes to C.U.P.- 2 planes in WAW, 1 in DOF... but I can't seem to get the Me-209 up and running in WAW. I never fail to get the 'Mission Loading Failed:Null' message when I try to fly it.
       Funny thing is, I installed it in the #SAS folder and when I select the SAS Modact module in my selector and run the game, I can fly it just fine- no issues whatsoever. So I know it isn't the plane... It is a sweet ride, isn't it?
       So, now for the logfile info... this section comes up every time I try to fly the 209:

Code: [Select]

Mission error, ID_04: java.lang.ArrayIndexOutOfBoundsException
java.lang.ArrayIndexOutOfBoundsException
at com.maddox.il2.objects.air.Aircraft.weaponsLoad(Aircraft.java:3308)
at com.maddox.il2.objects.air.Aircraft.weaponsLoad(Aircraft.java:3288)
at com.maddox.il2.objects.air.Aircraft.load(Aircraft.java:2853)
at com.maddox.il2.game.Mission.loadAir(Mission.java:1666)
at com.maddox.il2.ai.Wing.load(Wing.java:144)
at com.maddox.il2.game.Mission.loadWings(Mission.java:1344)
at com.maddox.il2.game.Mission._load(Mission.java:762)
at com.maddox.il2.game.Mission.access$600(Mission.java:120)
at com.maddox.il2.game.Mission$BackgroundLoader.run(Mission.java:463)
at com.maddox.rts.BackgroundTask.doRun(BackgroundTask.java:155)
at com.maddox.il2.game.MainWin3D.loopApp(MainWin3D.java:108)
at com.maddox.il2.game.Main.exec(Main.java:449)
at com.maddox.il2.game.GameWin3D.main(GameWin3D.java:235)
WARNING: ****( Unexpected txr reload (tfNoCompress16Bit,tfCompressMajorAlpha): '3do/Buildings/Troops/aircrew/pilot/glasses1.tga'
null
java.lang.NullPointerException
at com.maddox.il2.game.order.OrdersTree.getSection(OrdersTree.java:627)
at com.maddox.il2.game.order.OrdersTree.missionLoaded(OrdersTree.java:567)
at com.maddox.il2.game.order.OrdersTree.missionLoaded(OrdersTree.java:531)
at com.maddox.il2.game.Mission._load(Mission.java:897)
at com.maddox.il2.game.Mission.access$600(Mission.java:120)
at com.maddox.il2.game.Mission$BackgroundLoader.run(Mission.java:463)
at com.maddox.rts.BackgroundTask.doRun(BackgroundTask.java:155)
at com.maddox.il2.game.MainWin3D.loopApp(MainWin3D.java:108)
at com.maddox.il2.game.Main.exec(Main.java:449)
at com.maddox.il2.game.GameWin3D.main(GameWin3D.java:235)
[Jan 15, 2016 12:38:40 AM] -------------- END log session -------------

In this instance, I quit the game after the message, though I didn't have to, as there was no crash- I could have just selected another plane and gone on my merry way...
       The real-time log (eventlog.lst) does me no good in this case, because the mission never starts, therefore no data is recorded in that log at that time...

Thank you all in advance for any advice...   -Mike

 

[Darth_Dooboss]

The correct folder its the WAW.

Good luck and better flights

[MichaelZ]

Thanks for the reply-
        I'm sorry I wasn't clear about that. I did load the plane in the #WAW folder to use it in WAW... What I meant is that I also installed it in the #SAS folder to see if it would fly in that mode... which it did without incident. Which leaves me with my quandary- I installed it the same way in both folders, yet it works in one mode and not the other. My only hint is the 'Mission Error, ID_04:' that pops up in my logfile, whatever that error means...

Thanks again!  -Mike

[Darth_Dooboss]

Have you edit the air.ini, in STD\...\com and weapons & plane in \i18?

the aircraft must be only in the WAW folder not in the SAS

[Gatrasz]

I see 'Common Utils' are needed but they must be already included, so... My guess is that something in #WAW (heavily modded game, much more than the basic #SAS install) must be conflicting with Me-209 files.

[MichaelZ]

My guess  is some sort of conflict as well...
        After Darth's reply, I tried removing the plane from the SAS folder to see if it would have any effect on the WAW install, and it didn't. For giggles, I put it back in #SAS, left it in #WAW, and installed it in #TGA as well, where it also flew just fine! So I have the 209 flying in #SAS, flying in #TGA, but it still gives me the error in #WAW... ?
        I still wonder just what that 'ID_04' error is that the logfile keeps spitting out when I try to fly it...

Thanks for the advice!   -Mike

[MichaelZ]

IT'S ALIVE!!!!
         But, as usual, solving one problem begets another question... here's the thing:
I googled the text in the first line of my posted logfile segment- I found a page from a Java tutorial which kinda showed me where to look in the following lines...
         This led me to the 'Classes-ObjectsAir' folder. Opening that, then opening the 'cod' folder inside it, I saw a lot of rem'd files (with the minus sign added), which gave me an idea... I rem'd the entire 'cod' folder, then started the game. It worked! the 209 was operational, and no extra error entries of any sort in the logfile!
         At this point, I started disabling individual files, one at a time, and I isolated one file that was not allowing a mission to load with the 209 selected. The file is 59417938, modified 4/15/2013, size 1KB.
         I know that there have been others who have gotten this 'mission loading failed: null' when trying to use this plane- maybe this can help them.
         But can anyone tell me what that file does? And why it might snag things the way it did?

Thanks!  -Mike

[Griffon_301]

thats a dangerous road to follow!
the classes folder you mention contains a lot of class files for addon planes...so remming stuff out there or activating might lead to strange side effects...
might be more interesting to get the 209 mod itself, and then compare the classfiles from the mod with what you have inside the classes object.air folder;
to be honest, the 209 is one of those planes that has never been used in any campaign or mission and unless there is a campaign that uses it, i do not care if works or not...

[MichaelZ]

I couldn't agree more, Griffon... this is not my idea of a tidy solution at all.
       That being said, out of 46 files in that 'cod' folder, as it comes in part 17 of the WAW download, 21 were already remmed 'out of the box'... but still there in the folder. So, I didn't feel too bad remming out one more, and how much data could it have at 1 kb size?
       Nonetheless, you are absolutely right- the hot ticket would be to find out what's in that nasty folder and find out why it doesn't like the Me209, or why the plane doesn't like the info in the file. So how do we do this?

Thanks!   -Mike