PTE Build 82098-pte is now up!

Any ETA on some Server optimization , 50% of the games I play is slowmotion when we come to the 30-40 min of the game.

With SAO off and HDR on? That shouldn't happen. I've got a AMD GPU from the same generation, and for me, with the swapped shader order, and SAO deactivated, these dull colors are completely gone.

Looks still dull to me.


But I dunno how it even is supposed to look when it is correct.
Running a Radeon HD 7850 as well.

MY EYES

It doesnt fix it for me too btw. Running HD7850 too btw

@cola_colin Looks like @bgolus should get himself a 7850 as well.

Something is really, really wrong about that picture. I get the same result when I deactivate HDR, since the bloom shader is running havoc if HDR is not active.

So why isn't HDR working for you, like, at all?

I changed the position of the HDR calculation to be at the end of the pipeline, to cover all effects which had been disregarded previously. Without that change, it was bright for me as well, but not THAT bright.


Wait a moment... HDR did work for you. The average brightness is reasonable. But your skybox. It's much, MUCH darker than the stock one. Which would cause the HDR shader to trip as scenes with much of the skybox visible would be much darker on average.


That explains why it is so much brighter for you. So the bloom shader hits you double.


Well, next try. This time, I also removed bloom from the postprocessing pipeline, in addition to correcting the execution order. Please try with the new post.json, SAO and HDR on.

It appears as if SAO isn't faulty either, but only amplifies the effect of the bloom shader even more.

PS: Why isn't there a setting to remove bloom???

Checklist up to this moment:

• Bloom shader is broken on AMD GPUs
• HDR average is computed too early in the post processing pipeline
• HDR average sliding average depends on framerate(!!!)
• Checkbox for deactivating bloom is missing

That bloom bug... It looks much like the bug the bloom shader from original SupCom caused on AMD GPUs as well.

On an unrelated topic: The wireframe shader on the unit canon while under construction is ... wrong. The lines are much, MUCH too thin. Becomes very much visible when bloom is turned off.

And the unit selection circle needs a larger texture. That thing looks jagged when selecting larger buildings.

I am not using the stock skybox, so mine is different and maybe darker in some places.

On your newest post.json:

settings


and this happens when I turn off ambient occlusion and HDR with your post.json


Reminds me of what I had before at times. That is btw the day side. Night looks sorta okay.



Recently I play with the "no sun" mod and disabled shadows.
No sun = No brightness issues.

That one is really interesting. Because it means that your bug occurs independent from the post processing chain.

In the previous screenshot, about all the details visible have only been reconstructed by the SAO shader.

But your night time screenshot is wrong as well oO

Just as your daytime screenshot is just perfect, flat grey (all channels clipped at 0xac), your nighttime screenshot is completely tainted blue.

I don't see even the slightest trace of green, neither at day nor at nighttime.

So whatever happened, the color balance between night and daytime is completely off.


That would explain why the "no sun" mod fixes it for you - without sun, no broken day or nighttime. Great, that means that there is yet another bug. One more on the list....


Nonetheless, it's still wrong. If it looks always like the nighttime screenshot for you, it means that the colors are still missing.

Well I don't know if it is "fixed" without sun. But it looks okay to me.





HDR and AO is on, default post.json
Just no sun (however that is achieved) and a custom skybox

@cola_colin Ah sorry, mistook it for a different biome type. It's an ice, not a desert planet...

In that case, I think the day time screenshot with with new post.json (the one without bloom shader) actually looked the way it should look like.

Almost, at least. It takes 15-30 seconds before HDR adapts to the day side of a planet, thanks to that framerate dependency bug. Just zoom in on a location with vision coverage, and it should normalize quickly.

There still IS a bug somewhere earlier in the pipeline, which causes a bias, which then propagates, but it only trips the bloom shaders and it is catched by HDR when evaluated late enough.

Attachment now contains "instant HDR, no bloom" - full HDR adaption is a single frame. I don't think that slow HDR adaption was a smart idea to begin with. This is not an RPG or shooter where you remain in the same area for long, so HDR adaption shouldn't take anywhere as long as it does.

The other one has instant HDR adaption with original shader order. If bloom isn't bugging out for you, use that one.


PS: There is still something wrong with HDR
It's not sampling the entire scene. HDR only adapts to center of the scene, not the border. You can have the sun covering 1/4th of the screen, and it's not triggering HDR as long as the sun isn't centered...

The no sun mod you are probably using is Deep Space (I don't know of any others), which quite simply sets the ldr and hdr intensity to 0 in all the terrain jsons and kills the sun itself via the sun.fs file by setting its color to 0 (which I doubt will effect terrain at all). Basically a more extreme version of the AMD brightness fix mod.

Hope this info helps troubleshooting.

GOD BLESS RADAR FIXES

another request:

commander state when being idle ... also ui healthstate of comm ...

Radar fixed which is good. Still want Air & AA to be reworked.

.... like what?

maybe an attempt (successful?) to make HDR react to the planet and not to the background?

Don't know, but sounds plausible.

As far as it goes for me, I'm now personally satisfied with my post processing chain.

Instant HDR, HDR compose -> bloom -> SAO -> HDR average.

It's looking a bit dull on ice planets, but I think that's actually supposed to look like that.

Could someone package them as a mods and put them on PAMM? The no bloom one makes it even more eye friendly IMHO.

@mkrater if you would be so kind, please add a comment when you update the main post. Even just a few words so it shows up in the news feed.

- New AI personality setting enable_commander_danger_responses; always true
- A lot of tweaks to AI metal building - I had seen it stuck a few times in the last build
- One instance of PlanetCanBeUsedAsWeapon to changed to PlanetCanBeUsedAsKineticWeapon - possible new call (or maybe just renamed)
- Two new commanders (sale status TBD)

I'll throw them up as soon as github stops fighting me

EDIT: They are now up, I just called them Modded Post Processing Chain and Modded Post Processing Chain (no bloom) for lack of a better name. I have not tested them so let me know if I messed up somewhere.

Looks like they are working, thanks.