Bristol altimeter not indicating correctly

[=IRFC=Gascan]

Just after update 4.603, I noticed the altimeter for the Bristol is not indicating correctly. Actual altitude is significantly higher than indicated. This makes it difficult to perform photo recon missions on the FlugPark server, which requires flying in a particular altitude over the target area. It can easily be reproduced by starting any quick mission at any altitude above sea level and using simple gages to compare to the cockpit gage.

 

 

 

edit: can someone move this to bug reports? It seems I'm blind and missed that section of the forum...

Edited August 16, 2021 by gascan

[LukeFF]

The Bristol's altimeter has two different settings. 

[PaulTheSalty]

Does it? What is the key binding to shift it/ at what altitude does it need shifted?

[ST_Catchov]

3 hours ago, LukeFF said:

The Bristol's altimeter has two different settings. 

 

Do you mean metres and feet or something else? Gascan's images show the altimeter at 8000 feet and the simple gauge at 13117 feet. On the face of it, (no pun) the altimeter is showing the wrong reading, given that gascan indicates he's way higher than 8000 feet. Unless I'm missing something?

[RNAS10_Oliver]

9 hours ago, LukeFF said:

The Bristol's altimeter has two different settings. 

 

Are you referring to change between standard atmosphere and nearest friendly airfield?

 

Because although not mentioned here (is mentioned in his bug report) when online Gascan checked his readings against an DH4 he was flying with (me). Both our altimeters should have been set to standard atmosphere but were showing different results.

 

And the difference between standard atmosphere and nearest friendly airfield does not make such an large disparity as this, at least not when on the map and missions running on Flugpark.

Edited August 16, 2021 by RNAS10_Oliver

[=IRFC=Gascan]

Yes, as Oliver mentioned, when flying next to his DH-4, I we both swapped between standard atmosphere and nearest friendly airfield. The disparity was visible with both settings. These two screenshots were taken in a quick battle over water so the altitude above ground wouldn't throw anything off. I eventually found the bug report section of the forum (I may be a bit blind sometimes), and added the report there, as well.

Edited August 16, 2021 by gascan
mention the bug report

[PaulTheSalty]

Hopefully it gets sorted out soon. Does the currently bugged altimeter track up to ~8k’ and then stop, or does it track constantly while being incorrect?

 

Will have to test!

[LukeFF]

Nah, this has to be a map configuration issue of some sort - on the Arras Quick Mission map, the altimeter works as expected. I also tested the one in the S.E.5a, and it works the exact same way.

Edited August 17, 2021 by LukeFF

[J99_Sizzlorr]

8 hours ago, LukeFF said:

Nah, this has to be a map configuration issue of some sort - on the Arras Quick Mission map, the altimeter works as expected. I also tested the one in the S.E.5a, and it works the exact same way.

All other altimeters work fine on this particular map. I doubt that to be the problem.

[RNAS10_Oliver]

9 hours ago, LukeFF said:

Nah, this has to be a map configuration issue of some sort

25 minutes ago, J99_Sizzlorr said:

All other altimeters work fine on this particular map. I doubt that to be the problem.

 

I doubt also. A map configuration issue of some sort that impacts one type of aircraft in a formation but not the other types?

 

15 hours ago, gascan said:

Yes, as Oliver mentioned, when flying next to his DH-4, I we both swapped between standard atmosphere and nearest friendly airfield. The disparity was visible with both settings. These two screenshots were taken in a quick battle over water so the altitude above ground wouldn't throw anything off. I eventually found the bug report section of the forum (I may be a bit blind sometimes), and added the report there, as well.

 

Just for information. During the sortie where we compared our altimeter readings I hypothesized that the issue might due to graduations on the instrument having been changed (but not the needle animation) during the course of improving the cockpit textures. But just been going through some old footage and doe's not look as though the instrument has changed. So can rule that out. 

Pre 4.603

Post 4.603

[=IRFC=Gascan]

The two screenshots I posted were taken on the Kuban map, not Arras. I can take more screenshots on different maps and with different planes. I'll also swap the altimeter mode from standard atmosphere to nearest friendly airfield and back. Anyone else want to take a look as well, post some screenshots?

Edit: took some on the Moscow map as well. These two were taken with the Bristol F3 spawning in at 4km, and swapped the altimeter mode from standard to nearest friendly. The disparity is still very visible.

Edited August 17, 2021 by gascan
add screenshots

[JGr2/J5_Baeumer]

@gascan have you reported this in the bugs report section to 1C?

[J5_Adam]

Naaaaah it has to be the maaaaap

[RNAS10_Oliver]

4 hours ago, J5_Baeumer said:

@gascan have you reported this in the bugs report section to 1C?

Yes he has done. It’s not been acknowledged as yet.

 

 

[=IRFC=Gascan]

I recorded some video to show what I have been seeing, and added a second post on my original bug report to provide more detail. Has anyone else tried this in quick battle? Compare the simple gage or GUI instrument panel to the gage installed on the Bristol. There is also a button that can change between standard atmosphere and nearest friendly airfield (default is L-alt + A), but the discrepancy is still present.

 

 

[J99_Sizzlorr]

Is this bug acknowledge by the devs? It really makes things more complicated in the ww1 world.

[RNAS10_Oliver]

Same status as mentioned above. Reported but no response made by the devs in the thread to the report.

Edited August 30, 2021 by RNAS10_Oliver

[=IRFC=Gascan]

I got a "thanks" emoji from -DED-Rapidus. Not sure if that counts as the devs acknowledging it or not. Perhaps someone else can follow up with their own video or screenshot to prove its not just my computer that's messed up?

Edited August 31, 2021 by gascan

[1PL-Husar-1Esk]

2 hours ago, gascan said:

I got a "thanks" emoji from -DED-Rapidus. Not sure if that counts as the devs acknowledging it or not. Perhaps someone else can follow up with their own video or screenshot to prove its not just my computer that's messed up?

I do this. 

[ST_Catchov]

Is there an update from the beta testers or anyone else about the map configuration bug?

[1PL-Husar-1Esk]

52 minutes ago, ST_Catchov said:

Is there an update from the beta testers or anyone else about the map configuration bug?

What bug with map configuration , could you elaborate ?

[ST_Catchov]

50 minutes ago, 1PL-Husar-1Esk said:

What bug with map configuration , could you elaborate ?

 

Luke thinks that's the issue. He tested it. Maybe he could provide an update? 

 

On 8/17/2021 at 11:07 AM, LukeFF said:

Nah, this has to be a map configuration issue of some sort - on the Arras Quick Mission map, the altimeter works as expected. I also tested the one in the S.E.5a, and it works the exact same way.

 

[1PL-Husar-1Esk]

I tested it on Kuban map and Bristol altimeter was off but Se5 was fine,  same condition. 

[=IRFC=Gascan]

It is not map configuration. I tested on Moscow Winter, Kuban Summer, and Arras. All exhibited the exact same behavior. For now, the workaround for recon missions is one of two things: fly with another plane with accurate altimeter (this is how I figured it out in the first place) or use the bomb sight altimeter (which is in kilometers, but indicates correctly). I can now reliably perform the recon missions, but it really is annoying and resulted in several deaths, failed missions, and we failed to win a map the first Sunday we would otherwise have won because of it.

[J2_Trupobaw]

Is the bug consistent? Can Sizzlor update the recon missions and give indicated (rather than real) altitudes in Entente recon descriptions?

[=IRFC=Gascan]

It is consistent. However, we found a workaround. The bombsight altimeter indicates correctly. The only downside is the bombsight is in km while the mission description is in feet, but its not too hard to convert it and use that instead. I recorded a recon run for practice, will see about posting the video for training purposes later.

[J2_Trupobaw]

The missions could include walkaround by giving exact altitude in km and adjusted altitude in feet. I still encounter lost Bristols at 4k :p. 

 

It won' help the bug, but it will help the pilots. And I think the missions nees to be re-saved anyway when new game patch comes, so changing recon description back when bug is fixed can be done as part of that.

[NO.20_W_M_Thomson]

So this is why I couldn't do the recon last Thursday? Went to 9 thousand feet but could not trigger the photos.  

[Voyager]

Dumb question: for the reckons missions is there a command to do the photos or do they just happen automatically when you fly through the space? 

 

Is there any indication they happened? 

 

Been running recon missions in the campaigns and I have no idea if I'm doing them right or not. 

Edited September 12, 2021 by Voyager

[=IRFC=Gascan]

Thomson, Yes, this is probably why the recon didn't work for you. You can check your actual altitude by using the bomb sight. The target altitude for the recon is 2.7-3.3km, I believe.

 

Voyager, I am only familiar with the recon for the FlugPark missions and the Black September/Bloody April/Operation Michael multiplayer campaigns.  In those, you simply fly over the target at the correct altitude, and a subtitle will appear that tells you when you enter the area, when you exit the area, and when you have enough photos to head home. No buttons are needed to take the photos. I don't know about any other recon missions in other campaigns.

Edited September 12, 2021 by gascan

[=LD=Brazo]

Guys just wanted some feeedback. At treetop height I’m getting 1200 feet on the Bristol altimeter in the flugpark. Obviously not correct and Arras is 72m above sea level so also not the reason. Anyone else seen an issue lately with the Bristol?

Edited April 11, 2022 by 76SQN-Brazo

[=LD=Bulldog*]

I was Brazo's rear gunner at the time and I can vouch for the claim.