Hi i solved the problem a while ago and you are right i was using an outdated version of pureI'd wager you're running an outdated version of Pure. If i've mistakenly specified the minimum version too low, i'll fix that. Which pure are you using?
Hi i solved the problem a while ago and you are right i was using an outdated version of pureI'd wager you're running an outdated version of Pure. If i've mistakenly specified the minimum version too low, i'll fix that. Which pure are you using?
Simple adjustment to tone down the extreme sun blinding present with 1.44 on Pure 0.222
This does not include any other changes present in the currently Patreon only version 1.49, such as the new dynamic glare, reworked tone-mapping and improved colorspace work. That will be coming to a free release sometime 1.5X.
View attachment 726235
The moment has arrived! After a lot of work, the filter is in a great place for wider public release. What started as minor tweaking post 1.44, eventually evolved into a substantial rework of the color setup behind the tonemapping, additional support for new pure ambient lighting, implementing new glare presets, a dashcam mode, and was finally capped off with some interface cleanup.
Simplified calibration
In an effort to keep the PP tab of pure...
Forgot to re-invert a light setting, difference most ovious at dusk/dawn on non bounced light enabled tracks. Minor, but i'd prefer to not wait with this till the next update.
They are on the pp tab of pure config. If they are missing it's likely you installed the filter via CM. In this case I recommend reinstalling manually.Hey, this is amazing work, thank you for sharing with us. Just a rather silly question, probably. Where do I access the menu options shown in the main update page? I've flicked through the Pure menu when on track and I cannot seem to find those options. Thanks for pointing me in the right direction.
Yes, but it works well in HDR as wellWas this designed with HDR off?
Thanks.Yes, but it works well in HDR as well
That's certainly weird, i'll test the look with the shader off, but it generally shouldn't be more intense on default settings.I'm getting a really strong sun-facing effect, almost like the blinding one, even though I have the shader for blinding effects off. This didn't happen in the previous version. Is it meant to be like that in this version?
That's certainly weird, i'll test the look with the shader off, but it generally shouldn't be more intense on default settings.
Make sure you're running the required pure anc csp versions, and reset pure to defaultsRight so I installed this manually like advised and yes now I see the options shown in the screenshot. However, for some reason, any change I make to the settings seems to make no difference to the image. It used to, I switched to the "flat" option on one of the settings there, which greatly increased the brightness within the cockpit, but now when I change that same option, nothing happens on screen. None of the sliders affect the image, either. What could I have done to disable that? It's very strange, I cannot seem to get an image that I am happy with, without playing with those sliders (for me the image that I load into the track with is too dark).
this is the most intense i can get it, and that's with gadu spec godrays on.In case it helps, here's an example of what I mean. This disappears if I turn godrays to 0 in Pure's config. Couldn't find any settings within AEGIS that would work.
View attachment 727463
So all i can say is, make sure you're running the latest pure and csp, possibly reinstall filter completely, and reset pure to defaults.
Modifying bloom threshold shouldn't have any effect since that's controlled by the script. Are you sure the filter is installed correctly? Do you have all the filter specific options in the pure config pp tab?Tried it, but no luck. Tried adjusting some glare settings and setting the Bloom Threshold to 0 seems to work, though. Any clues...?
View attachment 727490
This doesn't seem to occur with other filters. Here's ILP with the same bloom threshold as default AEGIS.
View attachment 727477
Modifying bloom threshold shouldn't have any effect since that's controlled by the script. Are you sure the filter is installed correctly? Do you have all the filter specific options in the pure config pp tab?
yeah, that checks out. i've never heard of a track doing this, so doubtful. There is one thing that comes to mind, which did cause weird issues at some point. Check your documents\Assetto Corsa\cfg\extension folder, and look for a file named yebisest.ini if it's there, delete it, it no longer serves a purpose but can cause issues. Beyond that, i cannot explain this strange behaviour of the filterThink so. 13AEGIS.ini is under ppfilters, C13AEGIS.lua is under pure_scripts.
Options look like this.
View attachment 727495
Any chance this could be track-related?