Steering arrows
-
Normally those arrows follow the steer. But not to the edge of the screen. Anybody knows how to do it?
Would be useful for aiming in a dogfight with many ships involved when you just can’t see the steer properly.
-
0x75->0xEB in freelancer.exe, 0xC8864 = steering arrows always go to mouse 0xDC755C->0xF81A48 in freelancer.exe, 0xC885B = increase to 12 steering arrows PART 1 0x0000803F->0x6666E63F (1.0f->1.8f) in freelancer.exe, 0xC886A = increase to 12 steering arrows PART 2 0xDC6E5D->0x74864C in freelancer.exe, 0xC8AE0 = distance between steering arrows PART 1 0x90909090->0x9A99193E (filler->0.15f) in freelancer.exe, 0xC8674 = distance between steering arrows PART 2 0xE0755C->0x78864C in freelancer.exe, 0xC8A6F = size multiplier for steering arrows PART 1 0x90909090->0x0000003F (filler->0.5f) in freelancer.exe, 0xC8678 = size multiplier for steering arrows PART 2
- Depending on which version of Freelancer.exe you have, the filler bytes might be different (used for protection code).
- Twelve arrows will almost reach the left/right edges (for a 4:3 screen), and is more than enough for the top/bottom edges.
-
adoxa wrote:
0x75->0xEB in freelancer.exe, 0xC8864 = steering arrows always go to mouse
I guess this is it, will try.
Awesome!
Thank you very much indeed.P.S.
The word indeed comes to my mind not from Stargate SG-1, but from watching BBC World(I heard the hole phrase there) -
Is there any way to adjust opacity of these arrows?
Changing hud.ini and mouse.ini had no effect on the arrows
Now have no idea how…
-
Change the texture itself?…
-
Add Oc (1.0 is solid, 0.0 is invisible) to the material in DATA\INTERFACE\HUD\hud_steeringarrow.3db
-
shame on me!
Awesome, thanks.
continuing about HUD… is there any way to make shooting through the HUD possible?? Just press the right mouse button and here you go(it really annoys when you can’t do it).
-
Well, if I really find myself in a situation when I need to shoot through my HUD, I just disable it (backspace).
-
Here’s a solution that effectively gives preference to space, rather than the HUD. You’ll lose the flashing icons and tooltips, but it’s the best I could come up with.
filler->0x6A01FF1580725C00E9C5000000 in freelancer.exe, 0x19DD72 = shoot through HUD PART 1 filler->0x84E40F8834FFFFFF31C0C3 in freelancer.exe, 0x19DE44 = shoot through HUD PART 2 0x75->0x67 in freelancer.exe, 0x19D207 = shoot through HUD PART 3 0x79->0x6B in freelancer.exe, 0x19E103 = shoot through HUD PART 4 ```For the curious: Parts 1 & 2 test if the left button is down (GetKeyState( VK_LBUTTON )); if not the HUD is ignored. Of course, I would rather ignore the HUD if the right button is down, but that was only partially successful, and I couldn't track down why. Parts 3 & 4 simply point to the new code.
-
3/9