Just now, Parme said:

cessna 172 G1000

thanks

Ok. I'll give that a try and let you know.

14 minutes ago, Parme said:

cessna 172 G1000

thanks

Yes, I have the same problem with the Cessna 172 GS1000. The same VC commands work in the BS Baron and other planes I have used. If I find a solution I'll post here.

2 minutes ago, flyblueskies said:

Yes, I have the same problem with the Cessna 172 GS1000. The same VC commands work in the BS Baron and other planes I have used. If I find a solution I'll post here.

hmm great thanks, but do those planes have GS1000 aswell?

No, the BQ Baron does not have the GS1000. I just tried the Kodiak, which does have the GS1000 and it has the same problem. So, it appears that MSFS Agent is not compatible with the MSFS 2024 GS1000...that's too bad.

It does work in the Flight FX Citation X...

2 minutes ago, flyblueskies said:

It does work in the Flight FX Citation X...

Hmm interesting, i think its the event that is the problem , not the agent itself

24 minutes ago, Parme said:

Hmm interesting, i think its the event that is the problem , not the agent itself

I would agree. I did not see any other altitude events that might solve this. So, I would suspect a new event should be added and then recompiled. I wish I understood how to import the project, add the event, and recompile...but I don't.

Edited August 11Aug 11 by flyblueskies

17 hours ago, flyblueskies said:

I would agree. I did not see any other altitude events that might solve this. So, I would suspect a new event should be added and then recompiled. I wish I understood how to import the project, add the event, and recompile...but I don't.

Yeah that would be really cool to contribute to this lovely project and fill it with as many simconnect vars as possible

It looks like even the purchased HCS Voice Packs for Voice Attack and MSFS 2024 have the same issue:

20 hours ago, flyblueskies said:

It looks like even the purchased HCS Voice Packs for Voice Attack and MSFS 2024 have the same issue:

I’ve managed to get all the commands working now using AAO. It’s a completely other variable it uses and it’s not supported in the agent. But what i did now is that i created my own script for aao and call altitude , heading and verticalspeed from there instead. To compile a new dll for the agent was after some research way too complicated for me

46 minutes ago, Parme said:

I’ve managed to get all the commands working now using AAO. It’s a completely other variable it uses and it’s not supported in the agent. But what i did now is that i created my own script for aao and call altitude , heading and verticalspeed from there instead. To compile a new dll for the agent was after some research way too complicated for me

Sounds really good! Would you be willing to upload the Flightsim.to and share it?

Edited August 14Aug 14 by flyblueskies

12 hours ago, flyblueskies said:

Sounds really good! Would you be willing to upload the Flightsim.to and share it?

Hmm I’ve never done that but if you want I can help you in discord

2 hours ago, Parme said:

Hmm I’ve never done that but if you want I can help you in discord

Sure, which discord or is there a link?

9 hours ago, flyblueskies said:

Sure, which discord or is there a link?

wait, lorby helped me with everything on this forum, here is the link https://www.avsim.com/forums/topic/699647-communication-between-voiceattack-and-aao/page/3/#comment-5811629

9 hours ago, flyblueskies said:

Sure, which discord or is there a link?

(>A:AUTOPILOT·ALTITUDE·LOCK·VAR:0,·Feet) is the working AAO variable for G1000 altitude set ,