Dev's Limit Breaking 101 Techniques

Gisteron, if you have E0=A0+40 and CC=8C+40, how do you have 32 in A0 and 8C then? Sorry, but this explanation is not really helpful.

A0=(4+1)*20
the 8C is probably a sum of some values or does not define the 32 at all… sure adoxa can explain better xD
anyway, if adding 64 makes the maximal fire amount rise by 32, it is possible that other offsets define the initial 32. otherwise you could set the A0 byte up to FF (with equal risings of the 8C byte) resulting in (FF-A0)/2+32 maximal fires. but that’s obviously wrong.

edit: 0x_20_=32

A0=10*16=160

And you’re probably right on the initial 32.

@adoxa
sorry, for bumping this again… its about the nautical miles hacks. i used 2 decimal digits on the HUD and 3 on the contact list. i also set the “kilometers rather than meters” distance to 0 in the contact list and to 0.5N in the HUD. now, haven’t tested too much and figured out now, that some objects in the contact list still show kilometers.

@Gisteron: Using BPatch to apply and FL Hack to set the ranges, I don’t experience that. Either you’ve applied it wrong, or I need more information (I don’t see anywhere else it writes it).

Regarding the firing count. It’s a local variable (WORD hpid[32]) so it uses the stack. 8C->CC increases the stack usage (WORD hpid[64]); A0->E0 increases the offset for the argument. These are actually int values, so you can easily add more (2 * number, keep number even). So if you wanted to add another 32: CC00->0C01 & E000->2001. You got lucky with this since it was at the top of the stack; if it was at the bottom, I probably wouldn’t have bothered, since a lot more offsets would have to change (which is also why I restrict the system enumerator (best path finder) to ten rather than increasing it).

thank you, adoxa, found the problem: it was the 10k longint limit of D2C32, freelancer.exe (distance over wich fractions of kilometers are not displayed - Dev). i raised the value to 500k (just to ensure it results in the same for larger systems than NY) and all objects in the contact list that could be displayed were shown with nm distances.

It should work whatever the value is - I had nm at the default 10k.

well, i didn’t use FL Hack to apply anything about this one. only a hex editor. and all changes are exactly the hack you called (with decimals only), the range over which “kilometers” rather than meters are displayed in both HUD and contact list and finally the distance over which fractions of “kilometers” are not shown anymore.

guess it fits in here: is there a way to make the engine and trail effects disappear when you kill the engine? and btw where to find LODs of docking and running lights?

When it comes to extremely large CMPs (like planetary surfaces), once you face a direction opposite the center of the CMP, the model is no longer rendered and will simply disappear. Usually, this is not a problem - if a regular base is not rendered when you can’t see it anyway; but in case of a planetary surface, it is not like that.

Mostly this issue can be fixed by changing the radius of the CMP, but for some reason this does not work for objects of such massive size.

Is there any way to keep these objects rendered anyway?

SURs have a far greater impact on this than any CMP value you can set.

If your SUR mesh is the same as the CMP mesh it will not dissappear. Aslong as the SUR is visible in the screen it will render whatever it is attached too.

I’ve had a similar idea, but the SUR mesh is exactly the same as the CMP mesh - down to the point that even the CMP is nothing but convex meshes. I also get perfect hit and coll detection everywhere.
I think this needs a separate topic, not to waste space here. I will create one soon.

sumanuti wrote:

I did make a change to file but is it correct way?

How do you “Zoom in” close enough to see the numbers and letters in Hex editor?.

Cheers, Khayman.

khayman wrote:
How do you “Zoom in” close enough to see the numbers and letters in Hex editor?.

Cheers, Khayman.

When you start Hexplorer the first time you will probably want to increase the font size, it is a bit small for me. Click View… Options… and set Font: to Fixed Roman Large, and the Colors: to Matrix (or whatever combination you like).
.
.
.
Good luck.

Uncle StarTrader.

When you launch from a base and have just bought any weapon that uses ammunition, the weapon is deactivated by default. Is there any way to make them active by default? Thanks in advance!

freelancer.exe	07EBF1	0D->00 = activate missile/torpedo/disruptor on purchase ~adoxa
freelancer.exe	07FAA4	0D->00 = activate missile/torpedo/disruptor on mount ~adoxa

```Didn't find it for transfer (but didn't look that hard).

Thanks a lot!

is it possible to deactivate vsync in Freelancer per default?
A some ppl have probs to deactivate it via driver…

Update: These limits are cosmetic to the console only. The server will still prompt a default player limit.

I hope this is a good place to post this. After looking around for a while, I found no information for how to change the maximum limit of players for FLServer.exe. If this was posted before, ignore this.

This should be in the same notation everyone else posted in:

flserver.exe 006A3E 80->FF = Increases player multi count to 255, GUI Limit ~Omicron 
flserver.exe 006A3F 00->00 = Multiplier for player count, GUI Limit ~Omicron 
flserver.exe 006C45 80->FF = Increases player multi count to 255, Conditional Check ~Omicron 
flserver.exe 006C46 00->00 = Multiplier for player count, Conditional Check ~Omicron

This works for version 1.1 of FLServer, however it might also work on 1.0.

The “006A3E” offset is the actual player count allowed by the GUI box when you first start the server. By default, it is set to 128.

“006A3F” appears to be a multiplier for the last value. It is set to “00” above, but setting it to “01” multiplies the last value by 2. For instance, it you have it set to 255 characters, this will allow you up to 511 characters. “02” allows 767 in this case, and “03” allows 1023. As of current, FLServer resets input values over 999 back to zero.

The next two offsets are the values used in a conditional statement when you click “okay” on the GUI prompt. Rule of thumb, set these two values to the same values of the first two.