correct as is Taxi, Takeoff training mission doesnt advance

[ST0RM]

Tried the training mission the familiarize myself with the jet and bindings. The mission hangs on setting the altimeter. Airfield altitude is 1530 and when I set to match that and tap Space, nothing happens. It doesnt acknowledge. Just and FYI. Thanks

[Rongor]

Simply turn  the knob a bit further in both directions. 

At one point the script will be satisfied with your setting and continues

[MAXsenna]

Just press space, and turn knobs later.

[schmiefel]

On 7/27/2022 at 1:31 AM, MAXsenna said:

Just press space, and turn knobs later.

That was my workaround, too

More annoying is in my opinion that the highlighting sometimes hides the displays, buttons underneath (at least when using VR for the training), e.g. when you try to set the needed frequencies on the VHF radio the numbers get masked by this. For that I don't have a workaround so far and it doesn't happen only in the F1 but is a flaw of the DCS training system itself.

[MAXsenna]

8 minutes ago, schmiefel said:

That was my workaround, too

More annoying is in my opinion that the highlighting sometimes hides the displays, buttons underneath (at least when using VR for the training), e.g. when you try to set the needed frequencies on the VHF radio the numbers get masked by this. For that I don't have a workaround so far and it doesn't happen only in the F1 but is a flaw of the DCS training system itself.

Have you tried @Taz1004 "smaller training reticle mod", or whatever it's called? Just look up Taz in the user files. Not sure if it will help, but might be worth a try.

Cheers! 

[Flappie]

On 7/25/2022 at 1:23 PM, ST0RM said:

Tried the training mission the familiarize myself with the jet and bindings. The mission hangs on setting the altimeter. Airfield altitude is 1530 and when I set to match that and tap Space, nothing happens. It doesnt acknowledge. Just and FYI. Thanks

Expected value is slightly wrong (1520 instead of 1530).

Reproduced and reported. Thanks for the heads up.

[Flappie]

Devs answered me: it's correct as is. Slaved Altimeter initial pressure value is correct, and there's no need to change it. The altitude provided by the altimeter does not correspond exactly to the airport elevation, or the value given in F2 view.

[schmiefel]

And how does this solve the problem that the training doesn't advance at this point?

Plus: What's the standard procedure operating this aircraft - if there is no local air pressure information available (DCS still has no ATIS information or valid pre-flight briefing available), I thought its a common procedure to set the altimeter to zero for the current airport and going above a certain height switch to the standard pressure?

[MAXsenna]

7 minutes ago, schmiefel said:

And how does this solve the problem that the training doesn't advance at this point?

Plus: What's the standard procedure operating this aircraft - if there is no local air pressure information available (DCS still has no ATIS information or valid pre-flight briefing available), I thought its a common procedure to set the altimeter to zero for the current airport and going above a certain height switch to the standard pressure?

Like I wrote in a previous post. Just press space, and it will advance. Once for each altimeter though. 

Cheers! 

[schmiefel]

29 minutes ago, MAXsenna said:

ust press space, and it will advance. Once for each altimeter though. 

and that's the correct procedure: take the altimeter value as given even if its some hundred feet off of the current airport height ... really?

[MAXsenna]

1 hour ago, schmiefel said:

and that's the correct procedure: take the altimeter value as given even if its some hundred feet off of the current airport height ... really?

It's just a training mission in EA. Probably some issue with the trigger. 

It seems you know how to do this the correct way. 

Cheers! 

[schmiefel]

29 minutes ago, MAXsenna said:

Probably some issue with the trigger

Well I think that's the whole issue and its why it was reported as a bug. I was just a bit surprised as it was stated as 'correct as ...' above.

[MAXsenna]

1 minute ago, schmiefel said:

Well I think that's the whole issue and its why it was reported as a bug. I was just a bit surprised as it was stated as 'correct as ...' above.

True that. Need to check it again, to see the difference. If it is as large as you say, something feels off. But what do I know.  

Anyway, I always set it to zero anyway, after "spacing" in the training. On certain other maps, this won't work anyway, due to elevation.