Print

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

[Frankiek]

It is the first time that I am seeing this critical error in the log

BMPLoader bmp8PalTo4TGA4 s=PaintSchemes/Skins/P-36A-3/Hawk75 A3  P36 A3 France 1940.bmp s1=3DO/Plane/Hawk75A-3(Multi1)/summer s2=PaintSchemes/Cache/0
java.io.FileNotFoundException
   at com.maddox.rts.SFSInputStream.<init>(SFSInputStream.java:47)
   at com.maddox.il2.engine.BMPLoader.bmp8PalTo4TGA4(BMPLoader.java:375)
   at com.maddox.il2.engine.BmpUtils.bmp8PalTo4TGA4(BmpUtils.java:75)
   at com.maddox.il2.objects.air.Aircraft.prepareMeshSkin(Aircraft.java:2218)
   at com.maddox.il2.game.Mission.prepareSkinInWing(Mission.java:722)
   at com.maddox.il2.game.Mission.prepareSkinInWing(Mission.java:670)
   at com.maddox.il2.game.Mission.loadWings(Mission.java:656)
   at com.maddox.il2.game.Mission._load(Mission.java:278)
   at com.maddox.il2.game.Mission.access$000(Mission.java:37)
   at com.maddox.il2.game.Mission$BackgroundLoader.run(Mission.java:242)
   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:436)
   at com.maddox.il2.game.GameWin3D.main(GameWin3D.java:235)
INTERNAL ERROR: Can't open file 'PaintSchemes/Skins/P-36A-3/Hawk75 A3  P36 A3 France 1940.bmp'
INTERNAL ERROR: Bitmap 'PaintSchemes/Skins/P-36A-3/Hawk75 A3  P36 A3 France 1940.bmp' size: 0 != 512 | 1024

Usually if in a mission you don't have a specific skin the plane automatically use the default skin and mission goes on normally. However since I have adopted the HD dll the lack of skins causes a java.io.filenotfoundexception causing a CTD I wonder f this is normal I am on 409 with the latest version of the IL2selector (5.1.2) and the hd dll version is 04/05/2013.

Did someone face a similar problem?

full log here https://pastebin.com/yFxRk680

[bomberkiller]

Hallo Frankiek,

Had a similar problem two days ago, no idea what it was. At the bottom of the main games folder deleted the following file "~wrapper", restarted the game and everything was fine again.

As I wrote, don't know...!

Good luck and best regards

 

Gerhard

[SAS~Storebror]

~wrapper gets created when cache mode is activated in the selector.
In cache mode the selector will not scan the mod folders, instead it will use the cached file list from the ~wrapper file.
As a result, each time you change something in your mod folders, you have to delete the ~wrapper file so the selector will rescan the mod folders on next restart.
It has been an attempt to improve startup times in the early days of selector development but it is rather useless these days.
I'd recommend not to use cache mode anymore unless you have a really slow harddisk.
In a future version I might as well remove the cache mode from the selector altogether.


Mike

[Frankiek]

I don't have cache mode enabled (I barely use expert mode) and  I am running the latest version of the selector 5.1.

In my case the problem is linked to the HD dll and 24bit skin mod, as I don't see the error message in case of missing skins when I run IL2 with the "normal 2008 graphic dll

[bomberkiller]

In my case the problem is linked to the HD dll and 24bit skin mod, as I don't see the error message in case of missing skins when I run IL2 with the "normal 2008 graphic dll

Hello Frankie,

what's your game?

If #WAW3 go to "BATDOCS", "BATDLLS", dezip "BATDLLS-03_BAT-4096" in any folder (on desktop) and install the 4096² mod over again.

Good luck. 


Hello Mike,

Du hast den Nagel auf den Kopf getroffen! 

I turned off cache mode.

Thank you for the explanation.

Best regards

 

Gerhard

[Frankiek]

Not so uptodate this is still a 409 modact version tailored towards MTO and early war scenarios. The mission that gave me the crash is an old BoF mission.

The Carmaster DLL never gave me a problem so I think is rather the IES D520 the culprit as the game crashes when I am flying it. But if I try it in QMB even replicating the mission it goes well so is complicated. 

Could be combination as I have close to 400 entries in the air.ini so maybe I am close to the class limit and using a resource intense plane in a mission with plenty of activity and explosions make me run into memory errors.