Dev's Limit Breaking 101 Techniques
-
I believe my earlier post tells you how to remove non-targetted brackets around ships.
-
try to increase max distance that a ship can be selected to – 100000000f in freelancer.exe, 0x1D15B8, 0x1D15B8 = square of max distance that a ship can be selected — change to 1000000000000 or 10000000000
surprisingly it kinda worked(as far as i remember), still can select ships, but no unselected brackets.
may be not true, but seemed to work.
-
Some new hacks:
– 0x0F84->0x90E9 in freelancer.exe, 0x6AAF8, 0x6AAF8 = disable new player messages
– 0x0F84->0x90E9 in freelancer.exe, 0x6AF1E , 0x6AF1E = disable departing player messages
– Disable almost all hud elements. This is a horrible hack but hey it works. I’m sure someone could come up with a better hack for this but I got bored with tracing the code and cheated by overwriting the internal resource names.
In freelancer.exe: overwrite the byte at following addresses with 0x00
0x1D9368 = Disable lag icon
0x1D6E54 = Steering bar
0x1CB41C, 0x1CBCF8, 0x1CB3F8, 0x1CB3D4, 0x1CB3B0, 0x1CB38C, 0x1CB498 = Center top borders (but not buttons)
0x1CEB1C, 0x1CEB68, 0x1CEBB4, 0x1CEC08, 0x1CEC64, 0x1CECBC, 0x1CED0C, 0x1CED50, 0x1CED70, 0x1D8410, 0x1D81E0, 0x1D8204, 0x1D8228 = Right top buttons
0x1D7BFC, 0x1D7C04, 0x1D7D60, 0x1D7D90, 0x1D7DC0, 0x1D7DEC, 0x1D7E10, 0x1D7E70 = Center bottom - gauge borders & text
0x1D860C, 0x1D87E0, 0x1D8790, 0x1D8690, 0x1D86E0, 0x1D8668, 0x1D86C0, 0x1D86B8 =Right bottom - ship info - borders & text & icons
0x1D8CA8, 0x1D8C6C, 0x1D8C18, 0x1D8BE0, 0x1D8BA4, 0x1D8B6C, 0x1D8B34, 0x1D8AFC, 0x1D8AC4, 0x1D8A78, 0x1D8A3C, 0x1D8A0C, 0x1D89DC = Left botton - target info - borders & text & icons
0x1D9338, 0x1D9310, 0x1D92E8, 0x1D92C4, 0x1D92A0, 0x1D9278, 0x1D9250, 0x1D9224, 0x1D91F4, 0x1D91A4, 0x1D9184, 0x1D915C, 0x1D9134, 0x1D910C, 0x1D90E4, 0x1D90BC, 0x1D9094, 0x1D9068, 0x1D9538 = Targeting arrows
0x1D939C, 0x1D93D0, 0x1D9404 = Radiation and other misc items -
viper wrote:
with this Hack I always have an arrow rotating around my screen
And I’m not able anymore to klick on Ship to bring the focus on itThe arrow is your selection - FL can’t display the selection brackets because they don’t display on NON_TARGETABLE types (which is what FL is being tricked into thinking everything is). Just don’t select anything until you need to dock and it’ll be fine.
-
tnx for the answers
@Vital I test it but I still see brackets if the mouse goes over an unselected ship I want to remove the cursor completly so its an problem @M0tah ok in this way it works but im searching for a way to have this effects but I want still be able to select one single ship to focus on it in an vid
@Cannon very nice for making vids :))
any Ideas to solve my problem ?
-
Having managed to get widescreen resolution in Freelancer, I am looking for a way to edit the horizontal position of hud elements (the ones at the top middle and right and lower right middle and left for example).
I’m sure this has been asked before but I found information in the FL archive that says the positions of these elements are hardcoded into the exe, so I’m guessing this would be where offsets are required, does anyone have any information re: this?
-
Unfortunately, every single HUD element has it’s own position, so simply shifting the weapons info pane, for example, requires finding and changing a lot of offsets. I did a little work on this and had a somewhat long-term plan of making an interface editor program to allow the elements to be graphically rearranged and the new positions saved, but I don’t think that’s likely to happen anytime soon.
Anyway, here’s the incomplete list I compiled. The entries with ? at the end of the header means the offsets didn’t work like I thought they would. The “new” column is the value that adjusts the control for widescreen. Hope it helps.
(Controls: offset, original, new) -------- Weapon info background -------- X coordinate: 0xda9a4, 0.338699996471, 0.431699996471 (+0.093) Y coordinate: 0xda9a9, -0.243, -0.243 Scale: 0xda9b1, -0.91, -0.91 -------- Weapon info background minimized ? -------- X coordinate: 0xdaa25, 0.410100013018, 0.503100013018 X coordinate (2): 0xdaa7d, 0.40000000596, 0.49300000596 Y coordinate: 0xdaa2d, -0.370000004768, -0.370000004768 Y coordinate (2): 0xdaa82, -0.370999991894, -0.370999991894 Scale: 0xdaa35, -1.0, -1.0 -------- Weapon info number -------- X coordinate: 0xdab83, 0.270000010729, 0.363000010729 Y coordinate: 0x1d876b,-0.199000000954, -0.199000000954 Button height: 0xdab5c, 1.69999990612e-002,1.69999990612e-002 Button width: 0xdab61, 1.9999999553e-002, 1.9999999553e-002 -------- Weapon info name -------- X coordinate: 0xdabf4, 0.287999987602, 0.380999987602 Y coordinate: 0x1d8750,-0.199, -0.199 Button height: 0xdabd7, 1.69999990612e-002,1.69999990612e-002 Button width: 0xdabd9, 0.165000006557, 0.165000006557 -------- Weapon info ammo -------- X coordinate: 0xdac2f, 0.458000004292, 0.551000004292 Button height: 0xdac50, 1.70000009239e-002,1.70000009239e-002 Button width: 0xdac55, 3.99999991059e-002,3.99999991059e-002 -------- Weapon info close -------- X coordinate: 0xdad15, 0.38299998641, 0.53649998641 Y coordinate: 0xdad1d, -0.307000011206, -0.307000011206 Scale: 0xdad25, -0.5, -0.5 Button width: 0xdacfd, 1.40000004321e-002,1.40000004321e-002 Button height: 0xdad05, 1.40000004321e-002,1.40000004321e-002 -------- Weapon info use nanobots ? -------- X coordinate: 0xdad85, 0.340999990702, -------- Weapon info scrollbar -------- X coordinate: 0xdaefc, 0.490000009537, 0.583000009537 Y coordinate: 0xdaf04, -0.233999997377, -0.233999997377 Scale: 0xdaf0c, -1.0, -1.0 -------- Main Menu Button Backgrounds -------- X coordinate: 0x174671,-0.330000013113 Y coordinate: 0x1e3210,0.155000001192 -
Unfortunately, every single HUD element has its own position, so simply shifting the weapons info pane, for example, requires finding and changing a lot of offsets. I did a little work on this and had a somewhat long-term plan of making an interface editor program to allow the elements to be graphically rearranged and the new positions saved, but I don’t think that’s likely to happen anytime soon.
Anyway, here’s the incomplete list I compiled. The entries with ? at the end of the header means the offsets didn’t work like I thought they would. The “new” column is the value that adjusts the control for widescreen. Hope it helps.
(Controls: offset, original, new) -------- Weapon info background -------- X coordinate: 0xda9a4, 0.338699996471, 0.431699996471 (+0.093) Y coordinate: 0xda9a9, -0.243, -0.243 Scale: 0xda9b1, -0.91, -0.91 -------- Weapon info background minimized ? -------- X coordinate: 0xdaa25, 0.410100013018, 0.503100013018 X coordinate (2): 0xdaa7d, 0.40000000596, 0.49300000596 Y coordinate: 0xdaa2d, -0.370000004768, -0.370000004768 Y coordinate (2): 0xdaa82, -0.370999991894, -0.370999991894 Scale: 0xdaa35, -1.0, -1.0 -------- Weapon info number -------- X coordinate: 0xdab83, 0.270000010729, 0.363000010729 Y coordinate: 0x1d876b,-0.199000000954, -0.199000000954 Button height: 0xdab5c, 1.69999990612e-002,1.69999990612e-002 Button width: 0xdab61, 1.9999999553e-002, 1.9999999553e-002 -------- Weapon info name -------- X coordinate: 0xdabf4, 0.287999987602, 0.380999987602 Y coordinate: 0x1d8750,-0.199, -0.199 Button height: 0xdabd7, 1.69999990612e-002,1.69999990612e-002 Button width: 0xdabd9, 0.165000006557, 0.165000006557 -------- Weapon info ammo -------- X coordinate: 0xdac2f, 0.458000004292, 0.551000004292 Button height: 0xdac50, 1.70000009239e-002,1.70000009239e-002 Button width: 0xdac55, 3.99999991059e-002,3.99999991059e-002 -------- Weapon info close -------- X coordinate: 0xdad15, 0.38299998641, 0.53649998641 Y coordinate: 0xdad1d, -0.307000011206, -0.307000011206 Scale: 0xdad25, -0.5, -0.5 Button width: 0xdacfd, 1.40000004321e-002,1.40000004321e-002 Button height: 0xdad05, 1.40000004321e-002,1.40000004321e-002 -------- Weapon info use nanobots ? -------- X coordinate: 0xdad85, 0.340999990702, -------- Weapon info scrollbar -------- X coordinate: 0xdaefc, 0.490000009537, 0.583000009537 Y coordinate: 0xdaf04, -0.233999997377, -0.233999997377 Scale: 0xdaf0c, -1.0, -1.0 -------- Main Menu Button Backgrounds -------- X coordinate: 0x174671,-0.330000013113 Y coordinate: 0x1e3210,0.155000001192 -
Unfortunately, every single HUD element has its own position, so simply shifting the weapons info pane, for example, requires finding and changing a lot of offsets. I did a little work on this and had a somewhat long-term plan of making an interface editor program to allow the elements to be graphically rearranged and the new positions saved, but I don’t think that’s likely to happen anytime soon.
Anyway, here’s the incomplete list I compiled. The entries with ? at the end of the header means the offsets didn’t work like I thought they would. The “new” column is the value that adjusts the control for widescreen. Hope it helps.
(Controls: offset, original, new) -------- Weapon info background -------- X coordinate: 0xda9a4, 0.338699996471, 0.431699996471 (+0.093) Y coordinate: 0xda9a9, -0.243, -0.243 Scale: 0xda9b1, -0.91, -0.91 -------- Weapon info background minimized ? -------- X coordinate: 0xdaa25, 0.410100013018, 0.503100013018 X coordinate (2): 0xdaa7d, 0.40000000596, 0.49300000596 Y coordinate: 0xdaa2d, -0.370000004768, -0.370000004768 Y coordinate (2): 0xdaa82, -0.370999991894, -0.370999991894 Scale: 0xdaa35, -1.0, -1.0 -------- Weapon info number -------- X coordinate: 0xdab83, 0.270000010729, 0.363000010729 Y coordinate: 0x1d876b,-0.199000000954, -0.199000000954 Button height: 0xdab5c, 1.69999990612e-002,1.69999990612e-002 Button width: 0xdab61, 1.9999999553e-002, 1.9999999553e-002 -------- Weapon info name -------- X coordinate: 0xdabf4, 0.287999987602, 0.380999987602 Y coordinate: 0x1d8750,-0.199, -0.199 Button height: 0xdabd7, 1.69999990612e-002,1.69999990612e-002 Button width: 0xdabd9, 0.165000006557, 0.165000006557 -------- Weapon info ammo -------- X coordinate: 0xdac2f, 0.458000004292, 0.551000004292 Button height: 0xdac50, 1.70000009239e-002,1.70000009239e-002 Button width: 0xdac55, 3.99999991059e-002,3.99999991059e-002 -------- Weapon info close -------- X coordinate: 0xdad15, 0.38299998641, 0.53649998641 Y coordinate: 0xdad1d, -0.307000011206, -0.307000011206 Scale: 0xdad25, -0.5, -0.5 Button width: 0xdacfd, 1.40000004321e-002,1.40000004321e-002 Button height: 0xdad05, 1.40000004321e-002,1.40000004321e-002 -------- Weapon info use nanobots ? -------- X coordinate: 0xdad85, 0.340999990702, -------- Weapon info scrollbar -------- X coordinate: 0xdaefc, 0.490000009537, 0.583000009537 Y coordinate: 0xdaf04, -0.233999997377, -0.233999997377 Scale: 0xdaf0c, -1.0, -1.0 -------- Main Menu Button Backgrounds -------- X coordinate: 0x174671,-0.330000013113 Y coordinate: 0x1e3210,0.155000001192 -
Unfortunately, every single HUD element has its own position, so simply shifting the weapons info pane, for example, requires finding and changing a lot of offsets. I did a little work on this and had a somewhat long-term plan of making an interface editor program to allow the elements to be graphically rearranged and the new positions saved, but I don’t think that’s likely to happen anytime soon.
Anyway, here’s the incomplete list I compiled. All of the offsets are in freelancer.exe. The entries with ? at the end of the header means the offsets didn’t work like I thought they would. The “new” column is the value that adjusts the control for widescreen. Hope it helps.
(Controls: offset, original, new) -------- Weapon info background -------- X coordinate: 0xda9a4, 0.338699996471, 0.431699996471 (+0.093) Y coordinate: 0xda9a9, -0.243, -0.243 Scale: 0xda9b1, -0.91, -0.91 -------- Weapon info background minimized ? -------- X coordinate: 0xdaa25, 0.410100013018, 0.503100013018 X coordinate (2): 0xdaa7d, 0.40000000596, 0.49300000596 Y coordinate: 0xdaa2d, -0.370000004768, -0.370000004768 Y coordinate (2): 0xdaa82, -0.370999991894, -0.370999991894 Scale: 0xdaa35, -1.0, -1.0 -------- Weapon info number -------- X coordinate: 0xdab83, 0.270000010729, 0.363000010729 Y coordinate: 0x1d876b,-0.199000000954, -0.199000000954 Button height: 0xdab5c, 1.69999990612e-002,1.69999990612e-002 Button width: 0xdab61, 1.9999999553e-002, 1.9999999553e-002 -------- Weapon info name -------- X coordinate: 0xdabf4, 0.287999987602, 0.380999987602 Y coordinate: 0x1d8750,-0.199, -0.199 Button height: 0xdabd7, 1.69999990612e-002,1.69999990612e-002 Button width: 0xdabd9, 0.165000006557, 0.165000006557 -------- Weapon info ammo -------- X coordinate: 0xdac2f, 0.458000004292, 0.551000004292 Button height: 0xdac50, 1.70000009239e-002,1.70000009239e-002 Button width: 0xdac55, 3.99999991059e-002,3.99999991059e-002 -------- Weapon info close -------- X coordinate: 0xdad15, 0.38299998641, 0.53649998641 Y coordinate: 0xdad1d, -0.307000011206, -0.307000011206 Scale: 0xdad25, -0.5, -0.5 Button width: 0xdacfd, 1.40000004321e-002,1.40000004321e-002 Button height: 0xdad05, 1.40000004321e-002,1.40000004321e-002 -------- Weapon info use nanobots ? -------- X coordinate: 0xdad85, 0.340999990702, -------- Weapon info scrollbar -------- X coordinate: 0xdaefc, 0.490000009537, 0.583000009537 Y coordinate: 0xdaf04, -0.233999997377, -0.233999997377 Scale: 0xdaf0c, -1.0, -1.0 -------- Main Menu Button Backgrounds -------- X coordinate: 0x174671,-0.330000013113 Y coordinate: 0x1e3210,0.155000001192 -
Doing what I do, I’m particularly prone to crashes, so finally being fed up after waiting for the latest one, here’s a hexedit to disable dxdiag, which takes a long time to run.
0x81->0xC3 in freelancer.exe, 0x1A5390, 0x1A5390 = don't run dxdiag on crash ~adoxa -
If I enabled the ‘show order rep’ hack on the client side but not on the server side, might that cause the server to crash?
If so, would it crash only if you came in contact with the order (doesn’t happen in vanilla FL), or would it crash regardless?
