Had a boss who implemented code generation on one of our web applications. he basically transferred all the overhead of maintaining and writing good code to maintaining and writing his code generation / templating tool. it was absolutely boring, inefficient and stupid, and abstracted us all away from our real jobs.
Performance Issues? You won't BELIEVE how much fps is gained with this ONE TRICK!
- Thread starter DarkStarSword
- Start date
So... If a slight side-track is permissable...
These smoke (...and other) sprites -- they have this irritating behaviour of rolling along with the game camera - exponentially more annoying in VR -- would you say this is down to the manner in which the sprite/particle handling aligns axes, or could it be the shaders ignoring UVs, and using the textures straight-up in buffer space?
These smoke (...and other) sprites -- they have this irritating behaviour of rolling along with the game camera - exponentially more annoying in VR -- would you say this is down to the manner in which the sprite/particle handling aligns axes, or could it be the shaders ignoring UVs, and using the textures straight-up in buffer space?
Being a pig in mud with my new found fps, gave it another go.
Seems like this has deleted the volumetric fog shader? Its definitely missing from the tutorial and the usual places in stations etc.
Yep there's no off setting, just low... the one setting we couldn't have
I'll personally be running with it off still.
Seems like this has deleted the volumetric fog shader? Its definitely missing from the tutorial and the usual places in stations etc.
Yep there's no off setting, just low... the one setting we couldn't have
I'll personally be running with it off still.
Isn't the code for settlement fires going to be a hell of a lot more complicated than the mailslot smoke? It's not like they've just added more lines of code because they're mentally inferior to the people in this thread. Optimisations will happen, just probably not in the order any particular individual would like them to happen.
Intersting, and I have a question, as I'm not a coder: do you think the other various "blur" FX have the same effect on performance? There are quite a few in the settings.
If you're doing an A-B test use something like this to add a toggle button (this is what I used to take the two screenshots and compare before/after performance without moving the camera or otherwise changing state in a way that might have affected it):
Code:
[Constants]
global $show_smoke = 0
[KeySmoke]
key = z
$show_smoke = 1, 0
type = cycle
[ShaderOverrideBadPerformanceSmoke]
hash = cb9b58ca58c6c572
if !$show_smoke
handling = skip
endifYeah, I've noticed that. They've used a pretty typical billboard style effect without consideration that pinning "up" in a fixed direction relative to the screen isn't appropriate for a game like ED.
I might be able to find a way to filter out the smoke and leave the volumetric fog intact - 3DMigoto has multiple strategies that can be used to try to narrow down specific uses of identical shaders (e.g. matching the texture it is used with), however as I mentioned my intention isn't really to release a polished mod but rather bring attention to the issue.
In Odyssey they are the same shader - same code running on the GPU (not necessarily the same on the CPU - 3DMigoto only sees the GPU side). The shader has multiple if blocks, so it is likely that they enable/disable different parts of the shader depending on the situation where it is used (flow control is not very efficient on the GPU - most games trade off increased VRAM usage by having multiple (potentially hundreds) of faster shaders with one code path for each situation instead of one slow shader with many possible paths as this one has).
If you would enjoy the challenge, please release a mod. If such an expense is still present since last may, and they haven’t tried using the horizons version even, it can’t hurt to try something out of the community. Most a year is enough time to allow a more natural solution?
Maybe they’re just going through all the code sequentially without priority so who knows how long it’s going to take.
Last edited:
Sound familiar 
Thank you for giving a name (if we can call a hash a name) to this FPS monster
EDIT : i forgot the issue tracker.
Thank you for giving a name (if we can call a hash a name) to this FPS monster
EDIT : i forgot the issue tracker.
Last edited:
... and me!
Ps. Just in case you don't want to do a mod, this is mod enough. A button press to leave it on in space / off in settlements works fine!
good to know that there is still room for improvement!
consider posting it in this gem of a thread
the issue has already expired.Sound familiar
Thank you for giving a name (if we can call a hash a name) to this FPS monster
EDIT : i forgot the issue tracker.
consider posting it in this gem of a thread
Pay attention FD.
Bears repeating.
Actually, there still seem to be thriving communities behind the minimalist demo scenes and coding challenges. I've got a colleague who partakes in one of the European chapters and regularly codes 4 Kb C64 demos for competitions.
Extremely impressive and popular example from over a decade ago:
All eyeballing FD as a post hibernation snack.
I finally got the issue tracker to behave (lesson learned: disable privacy badger and other extensions when submitting a bug, otherwise all that time spent writing it up will be wasted and you'll have to do it all again - can you tell I'm salty?). Please vote for this issue:
I'm feel'n you CMDR. Here's the issue though. The OP is a workaround, not a fix. If FD implemented this workaround they would have to undo it once a fix materialized. There's no telling what catastrophe would result from such an endeavor. ...and there would be one.