Dev's Limit Breaking 101 Techniques

So, what about display more than one group member location icon on map displayer? It’s available in 1.0 but disabled on 1.1. Why it been disabled? how to get it back?

NeXoSE wrote:
So, what about display more than one group member location icon on map displayer? It’s available in 1.0 but disabled on 1.1. Why it been disabled? how to get it back?

You can see more than one group member on nav map with v1.0?

Yes, in 1.0 without any path. You can try it yourself, it’s really…

one thing about the nautical miles thingy: it works pretty well, as always, but the “N” is neither displayed in contact list nor on the target. on the target there is the float with “–” on the end and on the contact list there is the float with “-” on the end.

edit:
oh and as i am on it… and excuse me please for this request now…
the speed display is meters per second. how to make it show knots?
sorry, m8. just massively impressing work you are doing here, keep thyself in the bless our goodness brought you to.
deep bow down to thy toes.

See, I told you I do minimal testing (or, in this case, no testing :)). Updated the previous post, also including speed as knots. Please don’t ask me to change all the stats, as well…

I changed to two decimals, since three seemed a bit crowded on the Contact List. Assuming you’re using BPatch, say yes when it asks to apply anyway to use two; no to stay with three; or yes to the first and no to the second to use two in the List and three for the Target (change the patch to suit for the last two).

great, adoxa, all works geniusly

How I can make objects on a greater distance visible then in vanilla FL, without changing LODranges?

thanks

nice question… maybe a constant multiplier offset, another 1.0 float?

Easy enough to double or quadruple the existing LODranges, if that will do what you want (untested).

freelancer.exe    002389    83FE08->D8C090 = double existing LODranges PART 1 ~adoxa
freelancer.exe    00238C    7D16->9090 = double existing LODranges PART 2a ~adoxa
freelancer.exe    00238C    7D16->D8C0 = quadruple existing LODranges PART 2b ~adoxa

```Use parts 1 & 2a to double; parts 1 & 2b to quadruple. Bear in mind it replaces the test for eight ranges, which is the maximum allowed.

thx, but anyway I cant see objects on a greater distance then before…

I had assumed you’d already applied the maximum range patch.

freelancer.exe    1C8910    20000f = same offset as below, max distance at which ships can be seen (even if lodranges specify a higher distance) ~Dev
freelancer.exe    1C8910    20000f = same offset as above, poly flipping distance - raising this value stops graphical glitches on big CMPs, but raising it too high introduces flickering issues with SPH-based models (like planets) ~FriendlyFire

```This can be customized per system by using **space_farclip** in [SystemInfo].

freelancer.exe    0A8004    05->1A = show current worth in multiplayer ~adoxa

adoxa wrote:

freelancer.exe    0A8004    05->1A = show current worth in multiplayer ~adoxa

Works like a charm, thanks adoxa!

adoxa wrote:
I had assumed you’d already applied the maximum range patch.

freelancer.exe    1C8910    20000f = same offset as below, max distance at which ships can be seen (even if lodranges specify a higher distance) ~Dev
freelancer.exe    1C8910    20000f = same offset as above, poly flipping distance - raising this value stops graphical glitches on big CMPs, but raising it too high introduces flickering issues with SPH-based models (like planets) ~FriendlyFire

```This can be customized per system by using **space_farclip** in [SystemInfo].

And what difference between 1C8910 and 1C8910?

None. The same offset addresses two issues.

Just to give some extra info, this is essentially the far clipping plane, as adoxa also found an ini var with the same name.

If you raise the far clipping plane too much, you will get flickering issues because of z-fighting. The z-buffer loses precision quickly in the distance, therefore the larger the area covered by your clip planes, the more z-fighting (-> flickering) you will get.

I wonder, is there any possibility to prevent ships from automatically re-orienting themselves after you’ve vanilla FL’s x-y plane?

This what you want?

Thanks alot, made my day Completely other topic, but would it be possible to override the turret/weapon/torpedo limit?

I’m not sure what you’re asking. If you want more weapons, you have to modify the ship’s cmp file and its shiparch.ini entry to add hardpoints. If you want more ammo, use [Constants] MAX_PLAYER_AMMO in constants.ini. If you want separate limits for each ammo type, use this.