Dev's Limit Breaking 101 Techniques

That’s because FL can make cruise go slightly faster when you form up… I’m much more annoyed by how it continuously switches back and forth between 299 and 300.

As for limit cruise display, I guess it’d just be a matter of finding where the value to show is stored, change the comparison value too and you’d have it.

@Vital:

Gibbon, is it possible to limit cruise display limit to 600?
"Cos when you are grouping with npcs speed reaches 700+ sometimes? looks weired.

@Gibbon:

HUD Speed display limiter - Cruise

.004D592B: D815807E5D00 fcom d,[005D7E80 << Checking against 300.0, real(4) float

You just need to change the 300f to 600f (the same value is used for the check and display). The above disassembly shows the float in question is at 0x5D7E80. Subtract 0x400000 from that to get the file offset and you have 0x1D7E80. So change the 300f at 0x1D7E80 in freelancer.exe to 600f.

Thanks for the heads up there Motah. As i mentioned earlier this wasn’t my find, just a tutorial i had lying around which i didn’t see on the overall list. I knew the last part of what i posted worked as i now have tradelanes that show the correct speed, just not got round to testing the other bit yet lol

Gibbon, Motah - thanks, I should have read ALL of the Gibbon’s post… shame on me… :-[

Did anyone ever find a way to make the game render asteroid fields (the static roids not the dynamic ones) further away from the center of the system!?

w0dk4?

Depends how far we’re talking. I can have asteroid fields easily visible from quite some distance with no hack at all. It’s just a case of coding the custom asteroid ini properly

There’s about 300k from the systems center to the center of the field (position in the ini)

Everything except the static asteroids shows up! I know it’s not an ini problem, but a rendering distance issue…

Hey guys, i found something made me ….Er…

Ok, here it is:

– 6250000f in server.dll, 0x84ADC, 0x86AEC = square of NPC disappear distance in MP
– 6250000f in server.dll, 0x84ADC, 0x86AEC = square of maximum effect draw distance (vis_beam) ~FriendlyFire
– 6250000f in server.dll, 0x84ADC, 0x86AEC = square of distance from the center of the system over which bases no longer wish you well when un-docking (note: this is the same number as NPC disappear distance - as long as you have a good NPC persistance range, and good loot_unseen_radius = (radius) & loot_unseen_life_time = (time outside radius) in constants.ini, increasing this is safe) ~fox

And what exactly is the problem with those values? If you look at the top, you’ll see they’re for 1.0 and 1.1, respectively. The fact that they’re the same isn’t uncommon as most compilers will reuse identical constants as much as possible to reduce file size.

oh, still something to watch out for though when hacking the offsets

I just strange because there three different comment for the offerset, now your clear this point, thanks for reply guys.

Here’s one that may be of interest:

1.85f in Freelancer.exe, 0x1C9020, 0x1C9020 = aspect ratio of the cinematics

I’ve added a “Full screen cinematics” option to FL Hack. (It doesn’t modify that variable, but where it reads it, using the actual ratio of the resolution.)

While you’re at the cinematics, have you found a way yet to completely disable every undock sequence? I better ask first before I look into it myself and waste time

I haven’t, but I shall…

little question:

how do you find those hacks??

Disassembly listing (customised PeRdr) and debugger (Ollydbg).

Another really good one is Ida, it will also allow you to run the server and client in debug mode…

May I ask as a becoming C++ dev if and which of those programms are free(ware) software?

**Ida is very expensive, the current version is $539 (ouch).

Free version, quite limited
http://www.hex-rays.com/idapro/idadownfreeware.htm**