OHM Axial Velocity HUD v1.0 RC1

A VMT Hijacker would need to be careful with hooking clbkConsumeDirectKey and clbkConsumeBufferedKey as these could potentially break vessel functionality. Is there any reason why the char *keystate argument couldn't be changed to const?

Code:
    virtual void on_clbkConsumeBufferedKey ( VESSEL2* vess, DWORD key, bool down, [B][COLOR=Red]const [/COLOR][/B]char *keystate ) {}
    virtual void on_ret_clbkConsumeBufferedKey ( VESSEL2* vess, int, DWORD key, bool down, [B][COLOR=Red]const [/COLOR][/B]char *keystate ) {}
Ok, I'll add const to the keystate pointer, just to indicate that the hijacker shouldn't alter that, but honestly, if a person resorts to VMT hacks, I don't think it would stop him messing the contents of the array. :)

And perhaps also generally we could change the VESSEL2* to const also?
Well, I don't think so. This would restrict developer to calling only VESSEL::xxx() const methods (mostly 'getxxx'), which IMO servers no purpose -- one can easily and legally obtain a non-const VESSEL* via oapiGetVesselInterface().
 
Well, I don't think so. This would restrict developer to calling only VESSEL::xxx() const methods (mostly 'getxxx'), which IMO servers no purpose -- one can easily and legally obtain a non-const VESSEL* via oapiGetVesselInterface().
Fair call. :)
 
i have a little problem with this addon. its great, however, i have xr1 xr2 and xr5 and dgiv and lots of mfds. when i activate the module, and click on the dgiv it works. then when i try it with xr2, it doesnt appear, and even worse, orbiter.exe stops working, and i have to restart orbiter launchpad to use xr2 where it doesnt work! sorry if i sound rude.
 
Try this


Hi Astro

Yeah I was disappointed it wouldn't work with the superb XR2 either

HTML:
http://www.orbiter-forum.com/showthread.php?t=24219

I PM'd the author as suggested by Xyon, no luck :shrug:

Try the Surface MFD instead, you might need a couple of DLLs for it to work, just drop em in your ORBITER folder...
HTML:
http://www.orbithangar.com/searchid.php?ID=4388

Coupled with the XR2 AOA and SLIP gauges you'll get some precise touchdowns, albeit not as intuitively as with the HUD! :blackeye:


- B
 
Just for the record: the problem with incompatibility between Launch MFD and other VT hijackers is solved, using Agentgonzo's suggestion.

Solution:
[ame="http://www.orbithangar.com/searchid.php?ID=6023"]HUDDrawerSDK v.0.1[/ame]

Forum thread:
http://orbiter-forum.com/showthread.php?t=30520

Let the Axial Velocity HUD reimplementation begin!
 
Didn't work on my Taelon shuttle which is Class 3:( I made a class 2 and didn't work my class2 works now:)
 
Last edited:
Back
Top