Primarly related to VAS but maybe some other topics though ;-)
You are not logged in.
Hi experts,
It would be fine to be able to drive DH and MDA via IOCP. My goal is to modify their value with encoders (IOCARD).
Did you plan this kind of improvement?
Regards
Dan
http:\\ifair.fr
Offline
Hello Dan,
out of the top of my head the DH is sourced from the simulator. If you can access and modify it there, our representation should follow automagically. In that case no additional interface is needed.
Let us know your results.
Best regards,
Joe T. Hermann
Offline
Hello Joerg,
You're right. IOCP offsets are 1799 (Increase) and 1798 (Decrease).
I haven't check it!
Sorry
Regards
Dan
Last edited by GUDA (2010-03-17 14:55:46)
Offline
Dan,
you need my postal address for sending me the beer?
:-)
Joe
Last edited by joerg.hermann (2010-03-17 22:49:54)
Offline
Hello Joerg,
I've try ![]()
The 1798/1799 IOCP offsets have no effect.
I had a look on the 613 offset (decision height). If I change his value, nothing change in VASFMC. If I modify DH in VASFMC, this offset is not update.
I've look for FSUIPC variable without success.
Maybe these offsets are available only for FSX (I use FS2004).
Are you sure that VASMFC DH is based on public FS offset ?
Regards
Dan
Last edited by GUDA (2010-03-18 22:32:02)
Offline
Hello,
I've used FS-Interrogated to find a Decision Height offset.
I don't find any of variables.
I'm pretty sure that it's a VASFMC internal variable. As MDA
Regards
Dan
Offline
Dan,
the FSUIPC Offset your looking for is 0x3428, type FLOAT64.
GUDA wrote:
I had a look on the 613 offset (decision height). If I change his value, nothing change in VASFMC. If I modify DH in VASFMC, this offset is not update.
The TokenId 613 is the RAD/NAV Switch, the TokenId for Decision Height is 615. It's all in the FSUIPC SDK Docs.
Regards,
...........Adrian W.
Offline
Hello
When I talked about the 613 offset, it was about IOCP and not FSUIPC
Concerning FSUIPC and 0x3428 variable :
1 - FS-Interrogete2std : If I have a look on Hex-Viewer (8 bytes), the offset is updated when I modify the DH value with the mouse on the FS2004 panel
2 - VASFMC doesn't take into consideration this value
3 - If I change DH value in VASFMC, The FSUIPC offset is not updated
4 - If you stop/restart VASFMC, the MDA/DH values are lost, so I think that FS doesn't store these values.
So I continue to think that MDA and DH are internal VASMFC offsets.
Last edited by GUDA (2010-03-24 10:32:18)
Offline
I have checked the source code. DH and MDA are only internal variables (FMCData).
Offline