Dev's Limit Breaking 101 Techniques

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.

massdriver wrote:
replace actual texture in mat file not just transparency value.

Which .mat file?
I replaced textures with transparent .tga amongst those files that holds them - no dice! I dont see any other files that refers to these arrows.
Still I think Im not on the right path, cose colors of those arrows are hardcoded in FL.exe, and appearance can be modified through scanner distance / selecting ability. As soon they show up, you are able to select player.
Also, adoxa’s FLHack hides them, but from reason that my .exe is to much hacked, it refuses to start my FL without crash.

DATA\INTERFACE\buttontextures.txm

open with utf editor this file, look for “HUD_targetingelement” node it contains texture MIPs for all such stuff you need

WOW - thanks! That it is!
BTW, it is enough than just to comment out

;tex_shape = HUD_targetingelement
```in **buttontextures.ini** ![](http://i557.photobucket.com/albums/ss15/3MAJ/XsmileysX/crazy.gif)

[EDIT] - which than couses FLSpew to log

WARNING: ShapeDB: unable to find shape ‘HUD_targetingelement’

Guess I need that transparent.tga to implement, afterall ![](http://i557.photobucket.com/albums/ss15/3MAJ/XsmileysX/pfff.gif)

I found a bug with adoxa’s common.dll and server.dll hack to enable manual launching from docking bays. The Spew gave me the message```
WARNING:General:deform::start aim(): instance blocked – exiting

It seems that certain story-related events that are triggered by launch are not triggered any longer, if the hack is applied (it works just as soon as the original bytes are restored). I cannot tell if this is a problem related to the nature of the changes the hack makes. Please, someone more familiar with the engine, look into this.
Also, if there is no solution on the speciality modding side, perhaps someone here knows how to force trigger launching events independantly from launching mechanics.

Also, a completely unrelated thing I've realised was: there is a maximum cruise speed hardcoded. Any setting with conventional cruising or the multicruise plugin that'd exceed 1000m/s is reduced to a cruising speed of 990m/s with significantly higher acceleration time (that is otherwise dependant on mass and not only on the constant). Perhaps there is a way to reset this feature or remove this limit altogether.

as for the cruise speed, all you need to do is:
[PhySysConsts]
ANOM_LIMITS_MAX_VELOCITY = higher than cruise speed

Oh, wow, thanks for that!

I am a staff member on a server and we would like to know if there is a way to hide our location on the player chat screen.
I assume it’s a .exe or .dll tweak.
The server runs FLAC so FLHook is out of the question.

Smackdown wrote:
… we would like to know if there is a way to hide our location on the player chat screen…

maybe u can give adoxas territory plugin a try.
U can configure it how u like it to be (f.e. categorize them in “house system areas” or just let it display “sirius” @ every player)
it works pretty well for me

but i think there could be an offset change that simply overrides the clients “asking for locations”

*looking around for offset magicians *

If you’re trying to hide an admin’s location, using a clientside plugin to do it would be utterly useless. It’s trivially bypassed.

You’d need something on the server side, but I’m afraid FLAC development is near to non-existent around here. Unless someone can figure out a universal hack, you’re going to have a hard time.

I can modify TerritoryMP to work server-side (although it still requires client-side system entries). How should I determine if a player should be hidden (which would be achieved just by having a system called Hidden, or using an empty string)?

The server operator should have the option to choose who get’s hidden and be able to change it easily enough. Be it through a console command or something done to character files. And they could either just always be shown in New York, no matter where they are, or in ??? or something…
I’m sure whatever you come up with Adoxa will be a work of genius.

hey…
it wouldnt be limited to a console command, like smackdown said, a staff-dll would solve the problem too…it doesnt really matter. thanks man

~Rhodan

Went with a mounted piece of equipment, so you can even make it available to normal players, should you so choose. There’s one caveat: the first time you log in (after selecting a server), and you’re on a base, the equipment list hasn’t been created, so you’re still visible until a launch or reselection. Oh, I guess there’s another caveat, in that if you want to unmount the equipment and become visible again, you also have to launch/reselect to make it known. The Territory MP plugin is installed server-side now, so you can remove it from your clients (although it shouldn’t hurt if you leave it). However, as mentioned, the systems defined in universe.ini still need to exist client-side (as does the associated resource DLL), but you can hide the systems belonging to the territory, and/or the equipment hiding the system, from the client should you so choose.