Hello,

I'm finally back to flight simulation and started using MCE again now that I have a good headset for voice recognition. I'm using it with PF3 on P3Dv5 and have a few questions and remarks:

First of all, I can't see the text commands in red on the top left corner. Instead, the countermeasures are being toggled just like if I was pushing CTRL+Z. I tried the recover feature but it didn't help. Is there a way to get the FS commands instead?

Also, as explained in my other post, it seems there are some dlls missing from the MCE folders, but I guess you'll correct this in a patch.
A quick question about aircraft compatibility: is MCE compatible with the 737 Classic from captainsim? Or is it just compatible with their old 737s (737-100/200) ?

Another thing is that PF3 integration works pretty well with IFR flight plans, but I haven't been able to get a PF3 VFR flight plan to work correctly with MCE : PF3 absolutely understands nothing from what I say, and if by miracle it understands that I'm asking to open my flight plan, if I ask anything else after this, ATC keeps telling me "Okay will open your flight plan at ..." independently from what I'm asking. Using the hotkeys works as expected, but not with voice recognition. I can't verify if what I'm saying is properly recognized by MCE as I can't see the text commands as explained above. 

When using MCE with PF3, it seems that the FO has the control on radios by default, and if I'm asking for my IFR clearance, he will acknowledge for me immediatly, which can be quite annoying if I didn't understand correctly ATC. A simple tip is to tell him I handle the radio before initiating communications with ATC, but I usually forget to do so. Is there a way to get ATC control by default? 

Finally, PF3 documentation is actually the one for PFE, but since PFE, Dave has added quite a lot of new features to PF3, and some indications are missing: as an example, I struggled to ask for a direct to another waypoint as I don't know what to say exactly. Just asking for a direct to the waypoint name didn't work. I also was not able to ask for a higher altitude (it is documented though, but it didn't seem to understand what I was asking for).

 

EDIT: another last question, when FO talks to PF3 ATC, MCE seems to force the focus on P3D window, which prevents me from using my keyboard on others apps without risks of getting the landing gear out in the middle of the cruise, is there any option to prevent this?

 

Otherwise, now that I'm finally able to properly use MCE with a good microphone, I must admit it's really enjoyable !

Thanks by advance !

Edited October 21, 20223 yr by kmax59

1 hour ago, kmax59 said:

Hello,

I'm finally back to flight simulation and started using MCE again

Hello Maxime, glad to hear you finally back on simulation. Beside your growing experience with PF3 and MCE i hope there will be further steps on EnvX and Advanced EnvX again....😉

1 hour ago, kmax59 said:

First of all, I can't see the text commands in red on the top left corner. Instead, the countermeasures are being toggled just like if I was pushing CTRL+Z. I tried the recover feature but it didn't help. Is there a way to get the FS commands instead?

 

The menu commands recovery selection is mostly expected to be needed when you lload a flight that has "Flight info" saved with it. That means when you reload the flight, it looks like you lready pressed SHIFT+Z..

Having said that, the only other known scenario where the feature won't work is when a user has customized [TextInfo.x] sections in "prepar3D.cfg" or "fsx.cfg"

Only 3 sections are expected and they should be left at their default settings (No re-ordering of the items to be displayed).

Hi Gerald,

I'm using the default scenario as my default flight. However I have 5 info entries in my P3D.cfg, I've checked my default backup, and it's there as well, I didn't add anything, but if 3 section is necessary, that's something I can change myself.
 

3 hours ago, kmax59 said:

Also, as explained in my other post, it seems there are some dlls missing from the MCE folders, but I guess you'll correct this in a patch.
A quick question about aircraft compatibility: is MCE compatible with the 737 Classic from captainsim? Or is it just compatible with their old 737s (737-100/200) ?

Another thing is that PF3 integration works pretty well with IFR flight plans, but I haven't been able to get a PF3 VFR flight plan to work correctly with MCE : PF3 absolutely understands nothing from what I say, and if by miracle it understands that I'm asking to open my flight plan, if I ask anything else after this, ATC keeps telling me "Okay will open your flight plan at ..." independently from what I'm asking. Using the hotkeys works as expected, but not with voice recognition. I can't verify if what I'm saying is properly recognized by MCE as I can't see the text commands as explained above. 

When using MCE with PF3, it seems that the FO has the control on radios by default, and if I'm asking for my IFR clearance, he will acknowledge for me immediatly, which can be quite annoying if I didn't understand correctly ATC. A simple tip is to tell him I handle the radio before initiating communications with ATC, but I usually forget to do so. Is there a way to get ATC control by default? 

Finally, PF3 documentation is actually the one for PFE, but since PFE, Dave has added quite a lot of new features to PF3, and some indications are missing: as an example, I struggled to ask for a direct to another waypoint as I don't know what to say exactly. Just asking for a direct to the waypoint name didn't work. I also was not able to ask for a higher altitude (it is documented though, but it didn't seem to understand what I was asking for).

EDIT: another last question, when FO talks to PF3 ATC, MCE seems to force the focus on P3D window, which prevents me from using my keyboard on others apps without risks of getting the landing gear out in the middle of the cruise, is there any option to prevent this?

 

Sorry to insist, but what about these?
I've searched on the forum and PF3 forum already, but could not find any answer to these questions.

Edited October 21, 20223 yr by kmax59

3 hours ago, kmax59 said:

Also, as explained in my other post, it seems there are some dlls missing from the MCE folders, but I guess you'll correct this in a patch.
A quick question about aircraft compatibility: is MCE compatible with the 737 Classic from captainsim? Or is it just compatible with their old 737s (737-100/200) ?

Another thing is that PF3 integration works pretty well with IFR flight plans, but I haven't been able to get a PF3 VFR flight plan to work correctly with MCE : PF3 absolutely understands nothing from what I say, and if by miracle it understands that I'm asking to open my flight plan, if I ask anything else after this, ATC keeps telling me "Okay will open your flight plan at ..." independently from what I'm asking. Using the hotkeys works as expected, but not with voice recognition. I can't verify if what I'm saying is properly recognized by MCE as I can't see the text commands as explained above. 

When using MCE with PF3, it seems that the FO has the control on radios by default, and if I'm asking for my IFR clearance, he will acknowledge for me immediatly, which can be quite annoying if I didn't understand correctly ATC. A simple tip is to tell him I handle the radio before initiating communications with ATC, but I usually forget to do so. Is there a way to get ATC control by default? 

Finally, PF3 documentation is actually the one for PFE, but since PFE, Dave has added quite a lot of new features to PF3, and some indications are missing: as an example, I struggled to ask for a direct to another waypoint as I don't know what to say exactly. Just asking for a direct to the waypoint name didn't work. I also was not able to ask for a higher altitude (it is documented though, but it didn't seem to understand what I was asking for).

 

EDIT: another last question, when FO talks to PF3 ATC, MCE seems to force the focus on P3D window, which prevents me from using my keyboard on others apps without risks of getting the landing gear out in the middle of the cruise, is there any option to prevent this?

 

Otherwise, now that I'm finally able to properly use MCE with a good microphone, I must admit it's really enjoyable !

Thanks by advance !

CS 737 was only interfaced in FSX.

Never looked aty the new plane for P3D.

Could eventually get a 64 Bit dll compiled (from same source code) and assuming the plane in P3D uses the same custom variables and the plane is properly identified as 737 from CS it should work. Will post new 64 Bit dll tomorrow and you can have a go. May want to post "sim=whatever" from 737 aircraft.cfg

Yes, by default FO always has the comm from start. Won't be a big deal to add an option to let you have ATC from the beginning.

Yes, probably MCE needs to catchup with new features in PF3, but that will take time.

Rather than force you to speak specific messages, give me examples of ATC speech commands that come to you naturally and I'll check whether the speech grammar can handle your speech. Also, confirm which callsign you're using.

Believe it or not, The "force focus to the sim" was only requested recently by Bernd and was added to the very latest "fsInsider64.dll".

The purpose being to ensure PF3 never misses a hotkey

Only happens when you hold PTT down or FO is trying to reply or make a request.

 

Thanks for your answer Gerald

5 hours ago, FS++ said:

The menu commands recovery selection is mostly expected to be needed when you lload a flight that has "Flight info" saved with it. That means when you reload the flight, it looks like you lready pressed SHIFT+Z..

Having said that, the only other known scenario where the feature won't work is when a user has customized [TextInfo.x] sections in "prepar3D.cfg" or "fsx.cfg"

Only 3 sections are expected and they should be left at their default settings (No re-ordering of the items to be displayed).

So, I've removed the 2 additional entries that were there in Prepar3D.cfg (they were default entries). It didn't restore the fs commands text. I tried the recovers FS commands text, and it did not work either. As I said above, I don't use any custom scenario and didn't use SHIFT+Z at all.

 

3 hours ago, FS++ said:

CS 737 was only interfaced in FSX.

Never looked aty the new plane for P3D.

Could eventually get a 64 Bit dll compiled (from same source code) and assuming the plane in P3D uses the same custom variables and the plane is properly identified as 737 from CS it should work. Will post new 64 Bit dll tomorrow and you can have a go. May want to post "sim=whatever" from 737 aircraft.cfg

Yes, by default FO always has the comm from start. Won't be a big deal to add an option to let you have ATC from the beginning.

Yes, probably MCE needs to catchup with new features in PF3, but that will take time.

Rather than force you to speak specific messages, give me examples of ATC speech commands that come to you naturally and I'll check whether the speech grammar can handle your speech. Also, confirm which callsign you're using.

Believe it or not, The "force focus to the sim" was only requested recently by Bernd and was added to the very latest "fsInsider64.dll".

The purpose being to ensure PF3 never misses a hotkey

Only happens when you hold PTT down or FO is trying to reply or make a request.

 

1. There are actually two CS 737 now on P3D v3 to v5: The older CS 737 (which are the 100 and 200 variants) and the CS 737CL which are the 300, 400 and 500 variants. I can give a try to the updated dll but I guess it's for the older 737 then. Will there be any plan to support the 4/5/600 variants? It's not the same product from CS.

Here are the air files names for the classics:

y373_CFM56-3B1w
y373_CFM56-3B1
y374_CFM56-3C1W
y374_CFM56-3C1
y375_CFM56-3B1w
y375_CFM56-3B1

And here are the older 737 air files names (just giving you a few of them so you can check if it changed or not between FSX and P3D)
csx731
csx732
csx733

 

2. Adding an option to get the radios from the beginning could indeed be a nice feature 🙂 nothing dramatic that it's currently like this for now though

 

3. I tried the VFR flight plans with several callsigns, "N3817Z", and also, just as a test, "Ryanair 9525", the results were the same. Either ATC does not even answer, or the guy is stuck answering the same thing whatever I'm asking. Still can't confirm if it sends the correct commands as I am still unable to see them. It definitely comes from MCE as using the correct PF3 hotkey trigers the correct answer from ATC.
I wonder if the integration works well only in IFR as the PF3 hotkeys usually have different functions in VFR? Is this something that could be look into? VFR flights is probably where it's the most interesting to speak to ATC by voice, as you usually have much less time to search for the right hotkey and push it, and you usually don't have autopilot or copilot.

 

4. For the direct to waypoint, the natural thing that comes to my mind is to ask, for example "Ryanair 9525, requesting direct to ABBOT" we could spell the waypoint with military alphabet if that could help.

 

5. About the altitude change, I read somewhere that it's already supposed to be working, I asked things like "Ryanair 9525, requesting FL360" or "request further climb" or "request descent" or even "request descent to 6 thousands" or "6 thousand feet". Sometimes it didn't even answer, other times it just acknowledged "Roger Ryanair 9525" but I've never been cleared for the requested altitudes. 
I also tried to ask FO to ask ATC for the requested FL, he did understand me and ask ATC the FL I want. ATC understands but assigns a completely different altitude from what was requested.
Same as for VFR flight plan, using the correct hotkey works as expect so it must be something in MCE not sending the correct hotkeys.

 

6. Oh I see the reason then, well, I guess it could be problematic to remove the focus feature, or to add an option to disable it. It may be worth trying to find a solution, will let you know if an idea comes to my mind.

 

Sorry for the long post 😇

Edited October 21, 20223 yr by kmax59

18 hours ago, kmax59 said:

Thanks for your answer Gerald

So, I've removed the 2 additional entries that were there in Prepar3D.cfg (they were default entries). It didn't restore the fs commands text. I tried the recovers FS commands text, and it did not work either. As I said above, I don't use any custom scenario and didn't use SHIFT+Z at all.

 

1. There are actually two CS 737 now on P3D v3 to v5: The older CS 737 (which are the 100 and 200 variants) and the CS 737CL which are the 300, 400 and 500 variants. I can give a try to the updated dll but I guess it's for the older 737 then. Will there be any plan to support the 4/5/600 variants? It's not the same product from CS.

Here are the air files names for the classics:

y373_CFM56-3B1w
y373_CFM56-3B1
y374_CFM56-3C1W
y374_CFM56-3C1
y375_CFM56-3B1w
y375_CFM56-3B1

And here are the older 737 air files names (just giving you a few of them so you can check if it changed or not between FSX and P3D)
csx731
csx732
csx733

 

Thanks for providing the entries

Even re-ordering the items, like FPS first, then remaining VRAM will break it.

I suggest the following...

Save your current "Prepar3D.cfg" somewhere else, then delete it and let P3D generate a new one with default settings.

Start a new flight and the "Commands display" should definitely work.

If you reload a flight where info was saved, the menu "Recover text display" should work.

fsInsider64.dll hooks into the 3D info display text shown in the sim (unlike the green bar it's not shared with other add-ons nor does it hit performance as a result of laying a 2D window over the sim rendering window.

For technical reasons it can only display the MCE commands when it is in "FPS mode". Therefore, needs not only to know in which mode the display is in, so it can automatically SHIFT+Z to get it to that mode (and the reason it expects 3 modes), but also, the info display must match expected pattern, so fsInsider64.dll can see when P3D wants to display VRAM and temporarily replace the P3D text with MCE command.

If the pattern is wrong, like show coordinates first, followed by FPS, then whatever), it will just keep shifting+Z or exhibit some other odd behavior being out of synch.

We would have preferred to use the green bar for a simpler approach. Unfortunately, it's mostly useful for the odd message you output here and there.

When you start throwing speech commands at a heavy pace, not only will the constant green bar display hit FPS, but there is no guarantee it will display the speech command instatly because the requests to green bar are queued and must service other add-ons 

With regards CS 737

Blimey, that's a deluge of variants for the 737 from CS.

Currrently, only these will be identified

csx732
csx733

csx373

There is actually a 64 bit dll "mccs737.dll" to support them in P3D, assuming they are the same planes as the ones in FSX.

For other more recent planes, at the very least "mce.exe" will need to be updated sometime next week.

Then we'll find out whether the new 737s will need a completely new dll to interface them.

Edited October 22, 20223 yr by FS++

18 hours ago, kmax59 said:

Thanks for your answer Gerald

So, I've removed the 2 additional entries that were there in Prepar3D.cfg (they were default entries). It didn't restore the fs commands text. I tried the recovers FS commands text, and it did not work either. As I said above, I don't use any custom scenario and didn't use SHIFT+Z at all.

 

1. There are actually two CS 737 now on P3D v3 to v5: The older CS 737 (which are the 100 and 200 variants) and the CS 737CL which are the 300, 400 and 500 variants. I can give a try to the updated dll but I guess it's for the older 737 then. Will there be any plan to support the 4/5/600 variants? It's not the same product from CS.

Here are the air files names for the classics:

y373_CFM56-3B1w
y373_CFM56-3B1
y374_CFM56-3C1W
y374_CFM56-3C1
y375_CFM56-3B1w
y375_CFM56-3B1

And here are the older 737 air files names (just giving you a few of them so you can check if it changed or not between FSX and P3D)
csx731
csx732
csx733

 

2. Adding an option to get the radios from the beginning could indeed be a nice feature 🙂 nothing dramatic that it's currently like this for now though

 

3. I tried the VFR flight plans with several callsigns, "N3817Z", and also, just as a test, "Ryanair 9525", the results were the same. Either ATC does not even answer, or the guy is stuck answering the same thing whatever I'm asking. Still can't confirm if it sends the correct commands as I am still unable to see them. It definitely comes from MCE as using the correct PF3 hotkey trigers the correct answer from ATC.
I wonder if the integration works well only in IFR as the PF3 hotkeys usually have different functions in VFR? Is this something that could be look into? VFR flights is probably where it's the most interesting to speak to ATC by voice, as you usually have much less time to search for the right hotkey and push it, and you usually don't have autopilot or copilot.

 

4. For the direct to waypoint, the natural thing that comes to my mind is to ask, for example "Ryanair 9525, requesting direct to ABBOT" we could spell the waypoint with military alphabet if that could help.

 

5. About the altitude change, I read somewhere that it's already supposed to be working, I asked things like "Ryanair 9525, requesting FL360" or "request further climb" or "request descent" or even "request descent to 6 thousands" or "6 thousand feet". Sometimes it didn't even answer, other times it just acknowledged "Roger Ryanair 9525" but I've never been cleared for the requested altitudes. 
I also tried to ask FO to ask ATC for the requested FL, he did understand me and ask ATC the FL I want. ATC understands but assigns a completely different altitude from what was requested.
Same as for VFR flight plan, using the correct hotkey works as expect so it must be something in MCE not sending the correct hotkeys.

 

6. Oh I see the reason then, well, I guess it could be problematic to remove the focus feature, or to add an option to disable it. It may be worth trying to find a solution, will let you know if an idea comes to my mind.

 

Sorry for the long post 😇

2. Option will be added later.

3. To be honest, very little testing was done with PF3 and VFR flights. PF3 is better than default for IFR flights.

For VFR, have yet to see any ATC add-on do better than default FSX, Prepar3D ATC. No need to file a flight plan, contact whoever you want, say good-bye (or not), then contact any other ATC facility you want, state your intentions and eventually cancel them.

4. & 5.

I see you are using the wrong ATC phraseology. Let me explain

MCE tries to enforce good ATC practice, therefore the speech rule for making any request has this enforced rule

center_you_are_calling + your_callsign + request verbiage_variation + actual_request.   (in this order)

Examples:

Ground KLM 147 is ready for taxi

Ground KLM 147 standing by for taxi

Tower KLM 147 requesting takeoff clearance

By starting with center_you_are_calling, you are immediately drawing the attention of the controller so that he gets ready to listen to who is calling. If you start with "Ryanair 4321" at Stansted or Luton, you'll have all the Ryanair pilots on their toes waiting to see if the message is for them. Not good 😛

We used to enforce that rule for other requests like "Ground Ryanair 4321 we are requesting taxi" o "Tower Ryanair 4321 holding point 25 left, ready for takeoff". Because many users weren't trained pilots and didn't understand why no speech reco was working with ATC, we reluctantly updated the speech grammar to also use "Ryanair 4321 requesting taxi" or "Ryanair 4321 ready for takeoff", but it seems, we haven't done that for direct to or FL change.

So for now, use these

center_you_are_calling + Call_sign + requesting direct course to ABBOT

center_you_are_calling + Call_sign + requesting (further) climb flight level XXX

center_you_are_calling + Call_sign + requesting (further) descent flight level XXX

Speech grammar is very flexible in that it allows many moe variations like

center_you_are_calling + Call_sign + we'd like to climb flight level XXX

So, it's up to you. If you think enforcing good ATC practice is better, then try adapting to that.

Could eventuallly get speech grammar updated to accept your speech.

 

3. So I guess I’ll give another try to default ATC for VFR then

4&5. Of course I also tried by using the center_I_am_calling. As a real professional pilot that’s even the first thing I tried but it didnt work. as the copilot was not telling « center XXX ». I tried to use the same speech as him without success either, and tried all phraseology I could to get it working.

I also wasn’t able to get the FS text commands, which would be very useful to sort all those atc things out. Any idea about how to solve this?

 

1 hour ago, kmax59 said:

3. So I guess I’ll give another try to default ATC for VFR then

4&5. Of course I also tried by using the center_I_am_calling. As a real professional pilot that’s even the first thing I tried but it didnt work. as the copilot was not telling « center XXX ». I tried to use the same speech as him without success either, and tried all phraseology I could to get it working.

I also wasn’t able to get the FS text commands, which would be very useful to sort all those atc things out. Any idea about how to solve this?

 

There is currently a limitation with human recorded voice packs. MCE FO will only say "Frankfurt Tower" when using a TTS voice. Otherwise, you'll just hear "Tower".

Same with speech reco, with PF3, just use "Delivery", "Ground", "Tower", "Departure", "Center", "Approach".

You can try speaking a name but there is no guaranteed speech engine will pick-up the exact name of the center you spoke.

Agree, need to see what you are saying. So, let's get this thing going first.

Because you haven't used MCE for a while, I suggest you restore it to factory settings

Windows Start->Multi Crew Experience->Restore factory settings.

That will give you a new config file (mce.ini) in synch with latest added options and with default settings that include Always show spoken command.

You just need to ensure "Prepar3D.cfg" has all those  [TetInfo.1], [TetInfo.2], [TetInfo.3], .. as generated (unmodified) when the config file is first created and not just [flightInfo.1]

Anyone else not able to see spoken commands, please chime in.

Edited October 22, 20223 yr by FS++

On 10/22/2022 at 4:47 PM, FS++ said:

There is currently a limitation with human recorded voice packs. MCE FO will only say "Frankfurt Tower" when using a TTS voice. Otherwise, you'll just hear "Tower".

Same with speech reco, with PF3, just use "Delivery", "Ground", "Tower", "Departure", "Center", "Approach".

You can try speaking a name but there is no guaranteed speech engine will pick-up the exact name of the center you spoke.

Agree, need to see what you are saying. So, let's get this thing going first.

Because you haven't used MCE for a while, I suggest you restore it to factory settings

Windows Start->Multi Crew Experience->Restore factory settings.

That will give you a new config file (mce.ini) in synch with latest added options and with default settings that include Always show spoken command.

You just need to ensure "Prepar3D.cfg" has all those  [TetInfo.1], [TetInfo.2], [TetInfo.3], .. as generated (unmodified) when the config file is first created and not just [flightInfo.1]

Anyone else not able to see spoken commands, please chime in.

I'm actually using a TTS voice. But let's indeed focus on the text commands first. 
So I've made a backup of P3Dv5  P3D.cfg to generate a new one so it's default, I've restored factory settings then even uninstalled completely MCE, reinstalled it as an admin from a freshly downloaded installer. Didn't change any P3D or MCE option before trying.

The result is that it's still toggling the FS text info, but I can't get the text commands that are sent to voice recognition. The FS text commands recovery does not work either, so I'm out of ideas.

Here are the default Textinfo.X entries of my P3D.cfg.

Spoiler

 

[TextInfo.1]
AirSpeed=1,5
Altitude=1,3
Heading=1,4
Latitude=1,1
Longitude=1,2
WindDirectionAndSpeed=1,6

[TextInfo.2]
FuelPercentage=1,1
GForce=1,2
HealthPoints=1,3

[TextInfo.3]
FrameRate=1,1
GpuMemory=1,3
LockedFrameRate=1,2

[TextInfo.4]
AirSpeed=1,5
Altitude=1,3
FuelPercentage=2,1
GForce=2,2
Heading=1,4
HealthPoints=2,3
Latitude=1,1
Longitude=1,2
WindDirectionAndSpeed=1,6

[TextInfo.5]
AirSpeed=1,5
Altitude=1,3
FrameRate=3,1
FuelPercentage=2,1
GForce=2,2
GpuMemory=3,3
Heading=1,4
HealthPoints=2,3
Latitude=1,1
LockedFrameRate=3,2
Longitude=1,2
WindDirectionAndSpeed=1,6

 

 

I've tried on P3Dv4 and I can get the text commands, not on v5.

Edited October 23, 20223 yr by kmax59

7 hours ago, kmax59 said:

I'm actually using a TTS voice. But let's indeed focus on the text commands first. 
So I've made a backup of P3Dv5  P3D.cfg to generate a new one so it's default, I've restored factory settings then even uninstalled completely MCE, reinstalled it as an admin from a freshly downloaded installer. Didn't change any P3D or MCE option before trying.

The result is that it's still toggling the FS text info, but I can't get the text commands that are sent to voice recognition. The FS text commands recovery does not work either, so I'm out of ideas.

Here are the default Textinfo.X entries of my P3D.cfg.

  Hide contents

 

[TextInfo.1]
AirSpeed=1,5
Altitude=1,3
Heading=1,4
Latitude=1,1
Longitude=1,2
WindDirectionAndSpeed=1,6

[TextInfo.2]
FuelPercentage=1,1
GForce=1,2
HealthPoints=1,3

[TextInfo.3]
FrameRate=1,1
GpuMemory=1,3
LockedFrameRate=1,2

[TextInfo.4]
AirSpeed=1,5
Altitude=1,3
FuelPercentage=2,1
GForce=2,2
Heading=1,4
HealthPoints=2,3
Latitude=1,1
Longitude=1,2
WindDirectionAndSpeed=1,6

[TextInfo.5]
AirSpeed=1,5
Altitude=1,3
FrameRate=3,1
FuelPercentage=2,1
GForce=2,2
GpuMemory=3,3
Heading=1,4
HealthPoints=2,3
Latitude=1,1
LockedFrameRate=3,2
Longitude=1,2
WindDirectionAndSpeed=1,6

 

 

I've tried on P3Dv4 and I can get the text commands, not on v5.

It's possible the feature is broken in V5.3 as it can happen every now and then (for instance, it broke when they introduced GPU VRAM display) in V5. In that case it will need to be looked at.

Meanwhile, in case you are locking the frame rate, try unlimited, restart the sim and see if the text comes up as it does in V4

Eventually, remove section 4 & 5 and leave only these

[TextInfo.1]
AirSpeed=1,5
Altitude=1,3
Heading=1,4
Latitude=1,1
Longitude=1,2
WindDirectionAndSpeed=1,6

[TextInfo.2]
FuelPercentage=1,1
GForce=1,2
HealthPoints=1,3

[TextInfo.3]
FrameRate=1,1
GpuMemory=1,3
LockedFrameRate=1,2    (see if removing this one makes a difference)

 

Thanks

 

 

 

5 hours ago, FS++ said:

It's possible the feature is broken in V5.3 as it can happen every now and then (for instance, it broke when they introduced GPU VRAM display) in V5. In that case it will need to be looked at.

Meanwhile, in case you are locking the frame rate, try unlimited, restart the sim and see if the text comes up as it does in V4

Eventually, remove section 4 & 5 and leave only these

[TextInfo.1]
AirSpeed=1,5
Altitude=1,3
Heading=1,4
Latitude=1,1
Longitude=1,2
WindDirectionAndSpeed=1,6

[TextInfo.2]
FuelPercentage=1,1
GForce=1,2
HealthPoints=1,3

[TextInfo.3]
FrameRate=1,1
GpuMemory=1,3
LockedFrameRate=1,2    (see if removing this one makes a difference)

 

Thanks

 

Hi Gerald,

I've just tried your suggestions, unfortunately without success. Still the same result either by deleting sections 4 and 5, by unlocking frame rates or by using v4 entries. Removing the lockedframerate line also did not help.

Hello there,

Any news/ideas about the fs text commands not working on P3Dv5?

24 minutes ago, kmax59 said:

Hello there,

Any news/ideas about the fs text commands not working on P3Dv5?

After re-installing V5, starting from 5.0 it worked up to 5.1

Seems to have broken at V5.2

It is in the process of being mended.

Just be patient. This is important for us too.