4.11 General debugging

[E/CL Saburo]

Hi,
two red lights in Fw 190 A-4...A-6 cockpits (left up corner sign MG17) always light and indicated that MGs are broken even MGs are O.K.

Regards,
Saburo

[EJGr.Ost_Caspar]

Originally Posted by E/CL Saburo

Hi,
two red lights in Fw 190 A-4...A-6 cockpits (left up corner sign MG17) always light and indicated that MGs are broken even MGs are O.K.

Regards,
Saburo

No... in fact they should be yellow and show that the gun is charged/ready to fire. They also should be flickering while shooting (similar to Hs129 with 4xMG17 gunpod). So they have to go off, when the guns are empty, which at least they are in fact doing. I will stand in for a change here.

[Tolwyn]

Was just asking if you could add an option to supress (disable) the new Track Recording indicator for those of us that prefer not to see it.

[Snake]

Originally Posted by Tolwyn

Was just asking if you could add an option to supress (disable) the new Track Recording indicator for those of us that prefer not to see it.

How do u see it because I don't?!

[broadmarsh]

Overheat bug?

1. Flying Spitfire LF IXE CW 1944. The engine will overheat at anything over 73%. This is with 50% fuel and 500lb bomb.

Bomb delay bug.

2. With same configuration, I found the bomb delay does not stick on 2nd selection when jumping in and out of the arming screen.

a. Set it on 5 seconds or whatever you like in the Arming Screen and select Apply and Fly.

b. Then Refly, Arming screen and it is still at 5 seconds.

c. Select Refly and Arming and it is back at 0.0 seconds.

This has been tested on Warbirds of Prey Test Server 4.11. Set up today by RAF238thWildWillie

I was flying a test mission on WoP and was setting in the first instance a delay of 3 seconds and flying to the ground target and blowing up as soon as the bomb hit the ground and found on refly that when I went to the Arming screen it was back at 0.0 seconds. So in effect when I took off on a mission (after setting 3 seconds and apply) to bomb there was no delay. I did this 5 times! Perhaps 2 bugs!

Regards

RAF238GunRunner
(Sorry lost original login details)

[IceFire]

Originally Posted by broadmarsh

1. Flying Spitfire LF IXE CW 1944. The engine will overheat at anything over 73%. This is with 50% fuel and 500lb bomb.

2. With same configuration, I found the bomb delay does not stick on 2nd selection when jumping in and out of the arming screen.

a. Set it on 5 seconds or whatever you like in the Arming Screen and select Apply and Fly.

b. Then Refly, Arming screen and it is still at 5 seconds.

c. Select Refly and Arming and it is back at 0.0 seconds.

This has been tested on Warbirds of Prey Test Server 4.11. Set up today by RAF238thWildWillie

I was flying a test mission on WoP and was setting in the first instance a delay of 3 seconds and flying to the ground target and blowing up as soon as the bomb hit the ground and found on refly that when I went to the Arming screen it was back at 0.0 seconds. So in effect when I took off on a mission (after setting 3 seconds and apply) to bomb there was no delay. I did this 5 times! Perhaps 2 bugs!

Regards

RAF238GunRunner
(Sorry lost original login details)

For the Spitfire... I did a lot of flying around on Bessarabia and Crimea and while keeping the engine in the 70-80 range for cruise is best, you should be able to go higher for short periods of time similar to most other fighters. I can't say that I flew the IXe specifically.

What map was this on? Temperature discussions are definitely impacted by the map being flown on as the ambient temperature has quite an impact.

[broadmarsh]

Originally Posted by IceFire

For the Spitfire... I did a lot of flying around on Bessarabia and Crimea and while keeping the engine in the 70-80 range for cruise is best, you should be able to go higher for short periods of time similar to most other fighters. I can't say that I flew the IXe specifically.

There has never ever been an overheat problem of such magnitude as this on any Spitfire on any previous releases. One would expect to fly at 90 to 95% all the time on ETO missions and stay within the normal temperature envelope. In fact on this mission I had to throttle back to 50% to get rid of the warning. This is a bug or poor implementation. Take your pick.

Originally Posted by IceFire

What map was this on? Temperature discussions are definitely impacted by the map being flown on as the ambient temperature has quite an impact.

Yes I understand the map being flown impacts temperatures considerably. I have been doing this for some considerable time and I have first hand experience in Real Life of engine testing.

It is Normandy1.

Perhaps I could give you the server address and load the mission for you to try? Send me a PM?

[Fall_Pink?]

Originally Posted by daidalos.team

@moderator: please make it a sticky

Please post any 4.11 bugs here with a detailed description except for those related to AI and 6DoF. Thank you.

Daildalos Team

Maybe a solution to the java crashes. I disabled "ProcessAffinityMask" in the conf.ini and set it to:

[rts]
;0 -> all available cpus (default)
;1 -> execute only on CPU 0
;2 -> execute only on CPU 1
;3 -> execute only on CPU 0 and CPU 1
;4 -> execute only on CPU 2 (quad core only)
;5 -> execute only on CPU 0 and CPU 2 (quad core only)
;6 -> execute only on CPU 1 and CPU 2 (quad core only)
;ProcessAffinityMask=2

Did not have any jvm.dll crashes anymore... really too early to tell, but looking good sofar. Please check if other get similar results.

Rgs,
FP

[Treetop64]

I'm glad you posted that. I just learned that, all these years, I've been running on just one CPU.

[Fall_Pink?]

Originally Posted by Treetop64

I'm glad you posted that. I just learned that, all these years, I've been running on just one CPU.

Well, ahem, that's not the reason I posted that... I was merely thinking about the ai dll.
I didn't have any java crashes anymore tonight, so maybe's something is going on here.

Although, some others reported it works fine when it's only associated with core 1. Afaik, il2 can only run on 1 core, but this extra dll can make a difference. Weird.

Rgs,
FP