Print

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

[ponyboy314]

The skins from this link are in x1024 /3 MB resolution. In my B.A.T they show up without problems: https://www.sas1946.com/main/index.php/topic,67824.60.html

... yep, but stock format is 1 Mb, that's probably why these skins don't show in his game, they need to be downsized to 8bit (256 colours) instead of 24 bits ... 

Here is the link for those who need them in stock 8 bit format ... 

Yep, that was it.  Downloaded the skins from that link and now, everything is working as the universe meant. 

I thank you.  Life is always better with a duck at your disposal.

https://www.mediafire.com/file/5iaz19m8sdj713v/J2F-DuckS.7z/file

[ponyboy314]

I have another stupid question (I seem to be stacking those up a lot lately).

I have tried to use this J2F Duck in FMB, but when I do, this happens to my FMB:




Just so we're all aware, this also happens when I try gio963tto's J2F.  And to clarify, no.  I have not had both mods in my mods folder at the same time.

I uninstall one before trying the other. 

Anyway, this only happens when I use either J2F in FMB.  Both work just fine in QMB. 

What is it with the Duck?  Is it just not duck season?

So, any idea what causes this?  I have never seen it before, and it only happens with either J2F Duck mod.


Thanx in advance.

[Frankiek]

Few modded planes in the past had this problem (Bf-109B-1 and 2, the CR.20 etc) the reason is normally some bug in one or more meshes in the plane in question. This problem is more recurrent in Franken planes due to the original mesh manipulation. It is quite difficult task to identify the faulty file. A possible workaround is to make all the manipulations concerning waypoints, targets  and similar using another plane and change it just before saving the mission carefully avoiding to open the plane tabs. In alternative you can work directly in the mission file  where is relatively easy to change loadouts, skins etc.  It is not ideal but until the author of the mod  or other goodwilling modder don't provide a fix this is the only solution.

[ponyboy314]

Few modded planes in the past had this problem (Bf-109B-1 and 2, the CR.20 etc) the reason is normally some bug in one or more meshes in the plane in question. This problem is more recurrent in Franken planes due to the original mesh manipulation. It is quite difficult task to identify the faulty file. A possible workaround is to make all the manipulations concerning waypoints, targets  and similar using another plane and change it just before saving the mission carefully avoiding to open the plane tabs. In alternative you can work directly in the mission file  where is relatively easy to change loadouts, skins etc.  It is not ideal but until the author of the mod  or other goodwilling modder don't provide a fix this is the only solution.

That idea about using a different plane and then just changing it to the one I want...not bad.  That's inspired.

I'll try that.  Couldn't hurt. 

Thanx a bunch.  I want that Duck!

[ponyboy314]

Few modded planes in the past had this problem (Bf-109B-1 and 2, the CR.20 etc) the reason is normally some bug in one or more meshes in the plane in question. This problem is more recurrent in Franken planes due to the original mesh manipulation. It is quite difficult task to identify the faulty file. A possible workaround is to make all the manipulations concerning waypoints, targets  and similar using another plane and change it just before saving the mission carefully avoiding to open the plane tabs. In alternative you can work directly in the mission file  where is relatively easy to change loadouts, skins etc.  It is not ideal but until the author of the mod  or other goodwilling modder don't provide a fix this is the only solution.

Tried, and the moment I changed the existing aircraft to the J2F Duck, I had that same problem. 

Oh well.  Life goes on.  Stay cool.