JB3DG
-
Posts
13 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by JB3DG
-
-
The only change I can tell as far as x64 ASM goes is that all your 32bit registers (EAX, EBX, EDI etc) have the E replaced with an R for QWORD registers. (ie for a 64bit int, EAX becomes RAX).
Otherwise, the asm format remains the same. You also cannot do inline ASM anymore but have to resort to masm files in Visual Studio.
-
That pretty much describes what is happening with the F-4E ADV then. Fortunately your aircraft specific profile feature has given us the workaround solution. Thanks.
-
Do I understand correctly that if passed through FSUIPC calibration, FSUIPC won't even trigger the axis events in FS, but will write the throttle values directly to the sim variables?
-
That has been verified. How do I enable the logging?
-
Hi Pete
I am getting reports from users having problems with throttle inputs via FSUIPC in P3D with the recently released Milviz F-4E ADVanced product.
I am masking the axis throttle set events from the simulator and redirecting them into my own code which then sets the throttle position A variable. When I try passing the inputs through FSUIPC on my side (I make sure that there are no throttle input events in P3D's controls) I get no problems, both when I use Send Direct to FSUIPC Calibration and Send to FS as normal axis.
However, some of our users are getting an odd problem where they can provide throttle inputs and our code gets it but then the throttles get reset back to idle when the hardware axis stops moving.
Any ideas?
Thanks
Jonathan Bleeker
Milviz Systems Programmer
-
Hi Pete
Do you have any idea which dll contains the flight model acceleration and velocity calculations? The reason I ask is I would like to hook directly into that function so i can be syncronized with the simulation in order to simulate an INS correctly but i am unsure of where to start.
Thanks
JB
-
Coolness. Thanks
-
Oops....my bad. I meant
Is there a reason for the range in the guide to be x1000 to x1FFE when in the Gauges.h it starts at x10000 and ends at x1FFFF?
-
Ok looks like its the latter that the user is needing. However a small descrepancy in the user guide. All FSX key events (eg KEY_TOGGLE_FUEL_VALVE_ENG1 or (>K:TOGGLE_FUEL_VALVE_ENG1) as it is done in XML gauges) have an associated hex ID number defined in the Gauges.h file starting at 0x10000 or as the user guide correctly states, 65536. The 3rd party Custom event point starts at 0x11000 and ends at 0x1FFFF or 131070 as the guide again correctly states. However the hex notation in the guide seems a little off.
Custom controls, without a name known to FSUIPC, can be assigned by selecting <custom control> from the drop-down list, and then entering its number in decimal (range 65536 to 131070 inclusive) or, if you wish, in hexadecimal preceded by an x (range x1000 to x1FFE)
Is there a reason for the out of range when in the Gauges.h it starts at x10000 and ends at x1FFFF?
-
Hi
I dont have a registered FSUIPC...dont really have a need for it since i know how to use Simconnect as a C++ programmer....
Anyways Im trying to help a tester at Milviz get his hardware to work with a project-in-dev. I have used custom key events throughout this project (the 0x11000 type). I went through the FSUIPC documentation but im a bit at a loss as to how macros are created to work with custom key events. Anyone here who can share?
Thanks
JB
-
Danged.....Thanks anyway though. Im guessing that the turbine engine simulation is not quite the same in FSX as it is in FS9 so it wont transfer over ? (aside from the new afterburner systems....)
-
Hi Pete
Im working on a project that requires me to control the thrust of a turbine engine directly in FSX. Since Simconnect doesnt allow this I was wondering if you know of some sort of hack to get hold of the variable in memory and control it?
Thanks
Jonathan Bleeker
Detecting throttle axis assignments
in FSUIPC Support Pete Dowson Modules
Posted
Hi Pete
If a FSUIPC user has assigned their throttle axis in FSUIPC (assume P3D is set to use DirectInput instead of Raw Input as that is a requirement on my side), what FSUIPC file do I parse and what do I look for in it to determine which device and which axis is assigned to the Throttle (or Throttle1/2)? I need to do this in order to support some custom Afterburner threshold settings for some military aircraft at Milviz and right now I have run into a snag in that my config manager only works if the user has a throttle axis assigned in the simulator controls menu, not FSUIPC.