Unfortunately no, but thanks for the tip nonetheless. Up until a good couple of windows updates ago windows defender used to cause performance hogs like this, but I no longer see its icon among the processes for a while now.Necropants wrote:Do you use acronis?
Ok, I have an idea what that could be. What game settings are you playing on? I was playing on all Epic during the first stage. There is one shader that I still haven't made a regex for (not because I can't, just haven't gotten around to it because it wasn't necessary for me yet), so it could be that is only fixed with the Epic setting, and perhaps you're on something lower? I'll look at that when I get to playing/fixing this today.Necropants wrote:Ok yeah there is something wrong in my install because it's not just the cutscene. Guess will try a clean install with your latest wip
screenshot attached please correct me if this looks normal. (rename to jps)
Sheesh, yeah, forum tells me the file is rejected because it's recognized as a possible attack vector, even if I rename it as jpg or txt. So here's a link: https://www.mediafire.com/file/v2vzsv9i ... /regex.iniNecropants wrote:Unsure if the forum stripped the attachment Dj-RK Also I am playing on epic settings.
Okay, so I do not think it's SLI in this case.DJ-RK wrote:Sheesh, yeah, forum tells me the file is rejected because it's recognized as a possible attack vector, even if I rename it as jpg or txt. So here's a link: https://www.mediafire.com/file/v2vzsv9i ... /regex.iniNecropants wrote:Unsure if the forum stripped the attachment Dj-RK Also I am playing on epic settings.
I've had the same experience - going to Win 8.1 made a huge difference in performance... heading to Kashyyk today as well!DJ-RK wrote:Glad you figured it out, and thanks for sharing what worked for you. I'll try to remember to mention that in the blog post.
Actually, on the topic of settings, I found earlier today that it is possible to turn AA completely off, and post processing down to low, which eliminates DOF and motion blur. To do so, go into the video settings and change one of the individual settings so that the overall graphics option changes to "Custom." Now, highlight custom, and press the enter key (or A button on Xbox controller), and then press the Esc/B button, and it will change the overall preset to "Low" (which wasn't available prior), setting everything to a Low setting, except for AA which will be off. You can now change the individual settings you want to how you want them, but careful because when you change something away from the Low/Off setting, you won't be able to go back down to it without redoing the whole trick again.
With AA off, it highly reduces a dithering effect on Cals hair. I don't know if this is something up with my setup or if maybe there was an update that caused this, but like I mentioned before for some reason my TAA blur kill fix stopped working for me on High and Epic AA settings, and only works on Medium now or Off. I also much prefer having the DOF effect completely off by leaving Post Processing on the Low setting.
I was experiencing some really bad performance and frequent game crashes while playing on Win 10, but today I started playing on Win 7 and it was much smoother (or at least consistent) and no crashes.
I've made it as far as Kashyyk now. There were some issues that I needed to fix on Zeffo, but not many. Unfortunately there's a bit of a conflict with volumetric fog/lights and water/SSR fixes. Both are correct individually, but when you have both effects overlapping and occupying the same pixels they don't play nice, and cause a bit of clipping (not a huge issue, but it's worth mentioning).
I'll be at it more tomorrow and will try to have an updated WIP for you guys for the weekend.
OK thanks a lot, but sadly with French keyboards "~" never works. I'll try with the gamepad, but some people may not have one.DJ-RK wrote:@Dugom: Really, the main keys to use are ~ for autoconvergence, F1 to cycle through HUD depth, F2 to switch between auto-depth waypoint markers or static depth for them, and \ to disable the HUD all together. I did have a few extra disable keys set up on other F keys, but those have mostly become unnecessary.
Open auto_convergence.ini in ShaderFixesDugomFirst wrote:OK thanks a lot, but sadly with French keyboards "~" never works. I'll try with the gamepad, but some people may not have one.DJ-RK wrote:@Dugom: Really, the main keys to use are ~ for autoconvergence, F1 to cycle through HUD depth, F2 to switch between auto-depth waypoint markers or static depth for them, and \ to disable the HUD all together. I did have a few extra disable keys set up on other F keys, but those have mostly become unnecessary.
Any easy way to stop autoconvergence into .ini file ? (I've succeed in Life is Strange, but can't find on Geforce forum or remember how I have done it...)
[EDIT]
Found it: (Well Google did after several attemps)
https://www.nvidia.com/en-us/geforce/fo ... orm-in-3d/
But it won't help here cause there is no y4 line in the .ini file.
Thanks.maurizioclaudio21 wrote:Open auto_convergence.ini in ShaderFixes
search
[Key Toggle Auto Convergence]
key = ~
$auto_convergence_enabled = 0, 1
type = cycle
run = CommandListShowAutoConvergenceHUD
replace ~ whit other key I used a
Yeah, that can also be achieved using the same steps I mentioned here: https://www.mtbs3d.com/phpbb/viewtopic. ... 40#p166381 . Absolutely makes the game much clearer and sharper.DugomFirst wrote:.Use this command line:
r.PostProcessAAQuality 0
It will completely disable AA and it is another game now !!!
Really shouldn't look like that. Have you tried changing some of your settings (see Necropants' response above) to see if any of that helps? If none of that helps can you please confirm what resolution/aspect ratio you're playing at?Chtiblue wrote:Excellent fix DJ-RK!
I do have black eye isse (right or left it depends) and water reflections like in the pics below
https://postimg.cc/XGvD8jCF
https://postimg.cc/G42QV72w
Using WIP4 ?Chtiblue wrote:I do have black eye isse (right or left it depends) and water reflections like in the pics below
Thanks for this feedback. So glad to hear you're enjoying this fix, but more specifically the auto-convergence. I tried (and failed) to get that working on quite a few games before I finally got it all figured out on my last fix (Trine 4), so the fact I'm now able to implement it fairly well is a satisfying achievement for me, however handling things like convergence is a very personal thing and a lot of people favour performance and personal comfort over things like, "Wow! This 3D effect is ALWAYS perfectRubini wrote:Hi DJ-RK,
Just a feedback. The fix is awesome, almost all things fixed. Working flawless here. The auto convergence is a must, sometimes consumes a few FPS but its much better with it.
" and I've only ever had people come in my fix threads asking how to turn these features off, never saying they've particularly enjoyed them... which I know is just a matter of, "you only hear about something when things go wrong, not when things go right," but it's nice to hear that something that I've particularly had a challenge in learning to implement (that I personally think is a wonderful feature) is equally enjoyed by someone else. So thanks for this simple, but important feedback to me!Yeah, there are a couple of settings you can modify to tweak the end result. Firstly, you'll need to open the auto_convergence.ini file found in the ShaderFixes folder.Rubini wrote:Speaking about auto convergence, is it possible to make it react yet more quickly?
Thank you! Working on JFO has helped improve my knowledge of working on UE4 quite a bit. When I worked on BL3, I pretty much had to start from completely scratch because the existing UE4 universal fix didn't work at all there. Of course I learned and fixed a lot while working on BL3, there were a few key things that I missed and struggled on (ie volumetric fog and lighting), and some concessions had to be made because I had to balance the amount of time spent on particularly challenging things vs progressing to get a releasable product. With JFO, it was easy to adapt all the work I had already done on BL3 here, which then opened up the opportunity to revisit and spend more time on those other, more challenging things and I'm glad I was able to make breakthroughs in these areas and feel like my own UE4 fixing knowledge is near complete. Although a UE4 universal fix exists, I feel confident in my own regexes as being easily adaptable and will continue to be my preferred tool for future UE4 fixes, and I'm somewhat proud of that achievement.costiq wrote:
Thank you DJ-RK! Amazing work.
Thanks man. I know how much you love Trine 4, and for me getting autoconvergence working there was absolutely essential. Took the fix from "just another fix in my portfolio" to being one of (if not the) top 3D showcases that I've made! I'll probably put out another update for T4 soon to use some of the settings I've learned in JFO here to eliminate the judder that occurs during cutscenes. Appreciate your feedback all throughout the process.thebigdogma wrote:Well done and SO much appreciated DJ-RK. I love the auto-convergence and Trine 4, IMO, just wouldn't have worked near as well without it.
Thanks by the tips. The most i play with that values more i like the autoconvergence. I play some old dx9 games with Tridef that also have an autoconvergence as you probably already knows. What we have here for 3dVision is yet better, because now i can adjust it to my likes. Very well done! (this is the first game that i´m playing with this autoconvergence feature with 3dvision).DJ-RK wrote: Yeah, there are a couple of settings you can modify to tweak the end result. Firstly, you'll need to open the auto_convergence.ini file found in the ShaderFixes folder.
If you want to speed up the transitions, then change the $slow_convergence_rate setting to a higher value.
If you want to make the auto convergence shader more sensitive to detecting when to make adjustments, then try changing the $slow_convergence_threshold_near and $slow_convergence_threshold_far values to something lower
That's awesome. Thanks for providing your settings and notes. I still have yet to spend a good, proper session of testing different ranges and how they interact with one another, so that's helpful for me to try your settings and see how they differ. And having as many different opinions helps, so if other people want to try Rubini's settings and let me know their preferences are that's welcome feedback as well.Rubini wrote:Thanks by the tips. The most i play with that values more i like the autoconvergence. I play some old dx9 games with Tridef that also have an autoconvergence as you probably already knows. What we have here for 3dVision is yet better, because now i can adjust it to my likes. Very well done! (this is the first game that i´m playing with this autoconvergence feature with 3dvision).
I´m using these settings:
; Whether to display the auto convergence HUD while adjusting. Set to 2 to keep
; the HUD visible all the time: 1
global $auto_convergence_hud_enabled = 2
(to see the values in real time to easy adjusts)
; Rate for the slow auto-convergence transition (convergence change per second): ( default 50)
global $slow_convergence_rate = 300.0
(this one was made to soft the convergence transition ... in this game you can run into narrow spaces quickly or just look around and find a very near object ... then for my safety (and old eyes) a slow transition is worse than a quick one. This is why i use 300 here.)
; Amount the convergence is allowed to get *closer* than the auto-convergence
; target before the slower auto-adjustment kicks in: (default 75)
global $slow_convergence_threshold_near = 30
(this made the work for me: no more any hurt to my eyes, dropping the convergence to average 80 for nearest objects.)
; Amount the convergence is allowed to get further than the auto-convergence
; target before the slower auto-adjustment kicks in: (default 75)
global $slow_convergence_threshold_far = 65
(limit the average max convergence to something near 290-300 what is really enough and allows less auto adjusts by time)
I adjusted the Popout bias using the Nvidia´s convergence keys to achieve +0.018, which works very well for me.
I also need to comment that no FPS drop is noticeable when autoconvergence is in use. Like i said, this game have a lot of micro stuttering and some can at first think that the autoconvergence is the culprite and its not.
Yeah, that's something that both I and our friend maurizioclaudio21 noticed. I hadn't gotten around to looking at fixing that, but here's a temporary override that maurizio provided me with that you can add to the d3dx.ini file at the bottom:Rubini wrote:Some more feedback that catch my attention among others that you already commented above:
- sometimes the Carl eyes have not iris (its just an white greyed eye)
Yeah. There's 2 main issues with reflections. First of which are the shiny reflections that occur during the opening scenes. Like I mentioned before, it's hard to try fixing those because they only exist in cutscenes. Interesting/annoying thing is that I'd estimate I'm about halfway through the game, and I haven't really seen any since. So because of that I haven't really gotten another chance at trying to sort those out, but will make my best effort before release (but if they're not too predominant elsewhere then I might not spend too much time here. I just *really* don't want to keep having to run through loading and a cutscene if that's the only place it's an issue).- some reflections are yet not ok when using Visual effects in High or Epic settings. This is easily noticeable at the first presentation level at the Starships external body at distance.
Oh, believe me, I've seen that dozens of times already, but like I said, how would you like to spend 1 min loading a game, another 3-4 mins to get to the point in the game and the cutscene where you can see it, just to have about 5 seconds to test one of hundreds of potentially different possible adjustments, and then knowing it'll be another 5 mins before you get your next shot? I don't disagree that is one of the easiest places to find it, but it's sadly inefficient, so for now I'm more focused on playing through the rest of the game, fix everything else during gameplay, and if I don't come across any other scenes that's easier to work with, I'll go back to that section and I'll make a token last effort (but that's definitely not something I'm going to bang my head against a wall for if unnecessary).Rubini wrote:Yep! maurizio fix works! Thanks!
You can see that broken starships reflexion in game just a minute ahead after a game start at Bracca, after the second cutscene at the ship scrap panoramic view.
I am nearing completion on a tool that will fix this problem. Fingers crossed.DJ-RK wrote:How would you like to spend 1 min loading a game, another 3-4 mins to get to the point in the game and the cutscene where you can see it, just to have about 5 seconds to test one of hundreds of potentially different possible adjustments?
Ooooh, that sounds awesome! Everything crossed.schwing wrote:I am nearing completion on a tool that will fix this problem. Fingers crossed.DJ-RK wrote:How would you like to spend 1 min loading a game, another 3-4 mins to get to the point in the game and the cutscene where you can see it, just to have about 5 seconds to test one of hundreds of potentially different possible adjustments?
DJ-RK wrote:Ooooh, that sounds awesome! Everything crossed.schwing wrote:I am nearing completion on a tool that will fix this problem. Fingers crossed.DJ-RK wrote:How would you like to spend 1 min loading a game, another 3-4 mins to get to the point in the game and the cutscene where you can see it, just to have about 5 seconds to test one of hundreds of potentially different possible adjustments?
This is very good news! Anxiously waiting for the releaseDJ-RK wrote: Edit: Scratch that. I just loaded up the intro sequence to check if some of my new regexes have already done the work for me, and I'm glad to say they have! Problem already solved. In fact, I daresay that I think this one may be 100% done at this point! Going to keep playing for the rest of the evening. If I don't come across any more issues I'll be posting it to the blog tomorrow.
. Lets wait for the final release. I will look at that point and talk back. Yes I did. Thank you very much for that! Just in time for the Steam sale for me to look for new fixing projects.stfparis17 wrote:Hello DJ-RK did you receive my modest contribution via paypal from your email address?
rshannonca@gmail.com
Rgds
stfparis77
