I got a bad laptop to play on, so to avoid lags and other fps drop issues, I play on rather low effects settings.
Problem is, some guns rely on higher effects only and there is no low quality base effect.
So, trying to dodge invisible shots and since you can't always keep an eye on the enemies guns orientation (it's rather small and pretty hard to see when in the middle of the action) avoiding damage is nearly as hard as trying to dodge a real bullet fired from point blank range x)
So my question. How can I possibly make them visible without changing the .ini files?
Is there some low fx fire animation or do I just change each and every single effect in the fx folder? (it would take a loooong time to do that but... yeah...)
Thanks for any useful answer from the dev team or other people with modding capabilities
I have the same problem with my hardware and the best way around that I found is lowering all settings but the effect ones wich I set on 3/4th. That way you see all shots and the workload for your Laptop is considerably lower still.
Freelancer alone isn't a very demanding game. Practically any system is able to run it, but in case of your missing effects I have a possible solution.
I found this board on the Crossfire forums relating to graphics cards unrecognized by FL. It might not work, and it's for a different mod, but the file it's talking about is still in Discovery (and it's safe to edit, as it's a .txt file, not .ini)
Sorry for the broken English on there. Let me know if it works. If it doesn't, at least I tried.
That is because Discovery Mod assets do not have low-quality values. This is why if you set your textures to a minimum, most Discovery ships using certain textures will turn Invisible. Adding them would double the mod size.
Well, not exactly double, but...you know.
--------------
PSA: If you have been having stutter/FPS lag on Disco where it does not run as smoothly as other games, please look at the fix here: https://discoverygc.com/forums/showthrea...pid2306502
----------
(09-26-2016, 01:57 PM)sindroms Wrote: That is because Discovery Mod assets do not have low-quality values. This is why if you set your textures to a minimum, most Discovery ships using certain textures will turn Invisible. Adding them would double the mod size.
Well, not exactly double, but...you know.
This is only true for ships, and even then the bigger issue is remodeling everything to incorporate proper LODs.
Weapon effects have a vis_generic entry defined in their ini file, and back in Disco's early days fx developers glossed over adding that entry, which is what the game uses when your settings are cranked down. End result is invisible guns. I'll go through and do a pass on them at some point to check which are missing.
I went through the weapons.ale.ini file and some don't seem to be linked to the beam.txm file. Dunno if this is why it's happening. Also, the beam.txm has only 3 or 4 texture nodes for projectiles.
I went through the weapons.ale.ini file and some don't seem to be linked to the beam.txm file. Dunno if this is why it's happening. Also, the beam.txm has only 3 or 4 texture nodes for projectiles.
Maybe that info is worth something.
That has nothing to do with it
Txm files used to add textures or animations to effects if an effect not linked to a txm file that means the effect does not using any texture from it
You have to look .ale files to see if its using a texture from beam.txm or not
If using it and not linked to beam.txm then effect will be invisible
But you said you can see projectiles on high settings so nothing wrong there
The thing you're looking for is effects.ini. Weapon fx are split into three parts, an impact, a flash, and a projectile. Under the projectile entries (abbreviated proj) there should be a line that says vis_generic = blahblahblah. If the vis_generic = line is absent, that means it doesn't call on any effect when your settings are turned down low.
You also can't edit these ini files, as even though the various effects inis don't affect gameplay at all, the admin team will just ban you for cheating anyway. Your only real solution is to wait for an update.