Print

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

[SAS~Storebror]

Aircraft used: Ilyushin Il-4
Explanation: On the Top Gunner view, the fuselage loses its paintscheme & turns to a neon-green colour. This does not happen with other DB-3 aircraft.

Can't confirm. Probably you have a conflicting mod in place.


Mike

[SAS~Storebror]

*update*

Current bugfix status for Hotfix 15:

Error while creating WeaponSlot Nr. 3: BombGunTorpMk13a1 (-12345) for Aircraft com.maddox.il2.objects.air.TBD1

Can't confirm. Anyone else with this error?

Aircraft used: Ilyushin Il-4
Explanation: On the Top Gunner view, the fuselage loses its paintscheme & turns to a neon-green colour. This does not happen with other DB-3 aircraft.

Can't confirm. Probably you have a conflicting mod in place.

All other reported issues have been tackled and fixed.


Mike

[SAS~Loku]

I just checked it, i can confirm that bug, i see fuselage mesh neon green on il-4 top gunner.Gloss1Do replication bug?.

[Frankiek]

Confirmed with clean version no mods nstalled

[SAS~Storebror]

I would love to fix this, but I can only fix things I can replicate.
Gloss1D0o material replication code is in place in the gunner's pit class and it gets called and processed with no error.




Mike

[Frankiek]

Checked my log and I couldn't find any error related to IL-4 so maybe the error is visible only on certain systems and/or configurations

However the log was indicating another problem

Error while creating WeaponSlot Nr. 3: BombGunTorpMk13a1 (-12345) for Aircraft com.maddox.il2.objects.air.TBD1

[SAS~Storebror]

Tried a dozen times now with different skins and different game versions.
Turns out the IL-4 is left untouched since UP3 RC4. Nothing changed.
I'm afraid one of you who have this issue needs to volunteer and run the game in "dump" mode, trigger the issue, and upload his whole "dump" folder for me.
I'm sorry but there's no other way to isolate why what you see isn't what I see.

Error while creating WeaponSlot Nr. 3: BombGunTorpMk13a1 (-12345) for Aircraft com.maddox.il2.objects.air.TBD1

See my bugfix status post before.
You have reported that error already, but you are the only one so far.
I cannot reproduce it so for the time being, unless reported by someone else, I consider this a user side error (conflicting mod installed?).


Mike

[Frankiek]

I checked for the IL-4 problem with my backup clean UP3.4 version and it was still showing the green fuselage mesh

[SAS~Storebror]

That's purely anecdotal unless someone provides me the dump.
Sorry to say but even if a thousand people get the green mesh, the only way to proceed is the dump.

[SAS~Loku]

I found it, DB3s and IL4 TGunner share the same 3D so it had to be a java issue, i dumped and compared DB3F and IL4 TGunner classes from the larest version of UP3 and found they had different material replacement code, i copied working code from DB3TGunner to Il4TGunner class and it works.

[SAS~Storebror]

Granted there's a code difference, but both versions work well.
To me that is.
Comparing the code there's no reason for each of them not to work either.

It still makes no sense...

[SAS~Storebror]

Let me explain the situation from a code point of view.

DB3 top gunner pits exchange the fuselage material in the "old fashioned" way, in the "reflectWorldToInstruments" method:

Code: [Select]

  public void reflectWorldToInstruments(float f) {
    HierMesh hierMesh = aircraft().hierMesh();
    Mat mat = hierMesh.material(hierMesh.materialFind("Gloss1D0o"));
    this.mesh.materialReplace("Gloss1D0o", mat);
  }
IL-4 top gunner pit has the modern version of this code.
In that newer code version, the material change happens in a "reflectPlaneMats" method.
But since this method never gets called directly by the base cockpit class, a variable "bNeedSetUp" got introduced, which makes sure that on first update of the cockpit, the material replacement method gets called.
This is the way used for many aircraft, it always works.
To make matters visible, I've added a few log output codes to the IL-4 top gunner pit, see source below:

Code: [Select]

    public void reflectWorldToInstruments(float f)
    {
        if(bNeedSetUp)
        {
            System.out.println("### CockpitIL4_TGunner reflectWorldToInstruments(" + f + "), bNeedSetUp=true");
            prevTime = Time.current() - 1L;
            bNeedSetUp = false;
            System.out.println("### CockpitIL4_TGunner reflectWorldToInstruments(" + f + "), calling reflectPlaneMats(), bNeedSetUp=" + bNeedSetUp);
            reflectPlaneMats();
        }
    }

    protected void reflectPlaneMats()
    {
        HierMesh hiermesh = aircraft().hierMesh();
        Mat mat = hiermesh.material(hiermesh.materialFind("Gloss1D0o"));
        System.out.println("### CockpitIL4_TGunner reflectPlaneMats(), mat=" + (mat==null?"null":""+mat.hashCode()));
        mesh.materialReplace("Gloss1D0o", mat);
    }

    public CockpitIL4_TGunner()
    {
        super("3DO/Cockpit/DB3-TGun/TGunnerIL4.him", "he111_gunner");
        bNeedSetUp = true;
        prevTime = -1L;
        prevA0 = 0.0F;
        hook1 = null;
        System.out.println("### CockpitIL4_TGunner <init>, bNeedSetUp=" + bNeedSetUp);
    }
And this is the result:

Code: [Select]

[2023-02-24 07:36:33.699 UTC +1] dT:    0 ### CockpitIL4_TGunner <init>, bNeedSetUp=true
[2023-02-24 07:36:37.000 UTC +1] dT:   51 ### CockpitIL4_TGunner reflectWorldToInstruments(0.4), bNeedSetUp=true
[2023-02-24 07:36:37.000 UTC +1] dT:    0 ### CockpitIL4_TGunner reflectWorldToInstruments(0.4), calling reflectPlaneMats(), bNeedSetUp=false
[2023-02-24 07:36:37.001 UTC +1] dT:    0 ### CockpitIL4_TGunner reflectPlaneMats(), mat=4734828As expected, all code works fine and the material gets replaced successfully.
No clue why this doesn't work for those who witness the green fuselage, and even more, why it only fails to work on the IL-4 but not on the hundreds of other aircraft that use the same coding scheme.


Mike