Dev's Limit Breaking 101 Techniques

adoxa wrote:
server.dll 0876C0 500d = jump gate/hole x- & y-axis entry point adjustment ~adoxa

I found this value when I switched the viewer to DOUBLE FLOAT (IEEE, 64bits). Is that correct? It stretches from 0x0876c0 to 0x0876c7. It’s also a single value. How do you adjust for each (x and y) axis?

Thanks much for doing this Adoxa.

robocop wrote:

sumanuti wrote:
Works like charm!
Again, thanks adoxa.

I like the video. Is that in single-player or multi-player?

MP - the Dyson Destroy is next mission!

How’d you get out after undocking?

Before HARD! Now EASY!

I was never able to get the generator/shield thing to work. ie. Kill the generators, the shield drops.

One stuff kills with fuse other stuff that wears a SHIELD.

Wow nice, thanks.

@robocop: The original value is indeed double, used for both the x and y axes. Since I wanted separate values, the plugin makes patches to convert the double into single, thus also making room for another value.

All right, if I’m reading the info correctly I need to:

• copy the plugin (jumpoutpt.dll and accompanying files) to the EXE folder
• add the jumpoutpt.dll reference to the library in dacom.ini and dacomsrv.ini and
• create a JumpOutPt.ini file in DATA\UNIVERSE with the following contents (example shown, not actual):

[JumpOutPt]
;default = 500, 500, -350 ; original values
Li02_to_Li01 = 500, 500, -350, 0 ; always on the right
Li03_to_Li01 = 500, 500, -350, 90 ; always on the top

Does EVERY hole need to be addressed, or only the ones that are changed from default?

robocop wrote:
All right, if I’m reading the info correctly I need to:

• copy the plugin (jumpoutpt.dll and accompanying files) to the EXE folder
• add the jumpoutpt.dll reference to the library in dacom.ini and dacomsrv.ini and
• create a JumpOutPt.ini file in DATA\UNIVERSE with the following contents (example shown, not actual):

[JumpOutPt]
;default = 500, 500, -350 ; original values
Li02_to_Li01 = 500, 500, -350, 0 ; always on the right
Li03_to_Li01 = 500, 500, -350, 90 ; always on the top

dacom.ini is not needed.
Change only from a server side, no mod update is needed.
Think so?

Does EVERY hole need to be addressed, or only the ones that are changed from default?

correct answer!

very good
thanks.

sumanuti wrote:
dacom.ini is not needed.
Change only from a server side, no mod update is needed.
Think so?

I’m not sure about that, the directions specifically state both. I’ll try it either way to see.

You need dacom.ini (client) for single-player or dacomsrv.ini (server) for multiplayer.

works great. my ship is facing the wrong way when I enter but perhaps if i rotate the jump 180 i’ll be fine.

Common.dll - maximum FPS
Altering this values and limiting with 60 fps works good for players that had around 170 fps. For me using same thing that had 75 fps, turns out that it lowers to 35 fps making the disadvantage again like it was before.
And yes, its a huge difference fighting 60 vs 170 fps!
Does some part missing to be finalized?

[EDIT] * WORKS! Only me have issues, the PC sucks so fps change from 35 - 60. Sorry 4 disturbance!

flserver.exe	008B70	81->C3 = don't run dxdiag on crash ~adoxa, He||oween

Noticed that the server after crash keeps this process running too

008B70.

Oh, sorry

Just to remove green/white/red arrows on screen edges is left for pure camera use. I know for FLHack - Clear, but this one is preferred more.
Any solution?

Even this hacks didn’t help.

sumanuti wrote:
this hacks didn’t help.

Open texture file of that arrow, make it empty or full transparent, done. Sure it wont disable rendering, but at least it will have similar result.

massdriver wrote:

sumanuti wrote:
this hacks didn’t help.

Open texture file of that arrow, make it empty or full transparent, done. Sure it wont disable rendering, but at least it will have similar result.

Most in DATA\INTERFACE\HUD
hud_lootarrow.3db
hud_nextenemy.3db
hud_nextsub.3db
hud_nonselectedarrow.3db
hud_nonselectedarrow.cmp
hud_nonselectedarrowhat.3db
hud_nonselectedarrowquotes.3db
hud_nonselectedplayerarrow.3db
hud_nonselectedreticle.3db
hud_nonselectedwaypoint.3db
hud_reticle.3db
hud_reticle_arrows.3db
hud_reticle_health.3db
hud_reticle_quotes.3db
hud_reticle_shields.3db
hud_selectedwaypoint.3db
hud_steeringarrow.3db
hud_target.cmp
hud_target_min.cmp
hud_targetarrow.3db
hud_targetarrowhat.3db
hud_targetarrowhealth.3db
hud_targetarrowplayer.3db
hud_targetarrowquotes.3db
hud_targetedobject.3db
hud_targethealth.3db
hud_targetshields.3db

got Oc Node with Value=0 in Material library and still I cant get rid of it!
Getting a feeling it must be hacked, cose transparency of that arrow is dynamical.

Sure that’s a walkaround rather than a solution, but you might as well replace the spot the texture with a fully transparent one. That at least is a conventional way to get the goal…

replace actual texture in mat file not just transparency value.