OK I was just looking at the rez zones seems they are in fact a bit broke. It appears to be a one eye type issue.. I made a screenshot ignore the black line down the middle it is an artifact from nThusim for my curved screen..
Note the one eye effect asteroid shadows appear there in one eye and gone in the other.. I looked at it but have no idea how to repair that issue.. I did try the flag in the ini it did not fix it..
OK I was just looking at the rez zones seems they are in fact a bit broke. It appears to be a one eye type issue.. I made a screenshot ignore the black line down the middle it is an artifact from nThusim for my curved screen..
Note the one eye effect asteroid shadows appear there in one eye and gone in the other.. I looked at it but have no idea how to repair that issue.. I did try the flag in the ini it did not fix it..
Asteroid belt fix would be very nice as it can be very irritating at some places. I'll try to get a good example of the Conda and Corvette hull reflection glitches, but it could take a while till I can get back into the game.
Asteroid belt fix would be very nice as it can be very irritating at some places. I'll try to get a good example of the Conda and Corvette hull reflection glitches, but it could take a while till I can get back into the game.
Well the more I been looking at this problem it seems the shadows are broke again.. I was in the cockpit and looked left and notced the one eye effect with the shadow there..
I may disable them for now but I think we have the option to turn them off in options..
Well the more I been looking at this problem it seems the shadows are broke again.. I was in the cockpit and looked left and notced the one eye effect with the shadow there..
I may disable them for now but I think we have the option to turn them off in options..
Bad news btw ... I just tried the current fix on the open 2.3.10 beta, and it looked absolutely bonkers.
Funnily, the previous "Elite+Dangerous+Fix+Beta+v1_2" and even the ancient "EDHorizonsv18.6-win7-64bit" worked considerably better and were at least bearable on the eyes.
Bad news btw ... I just tried the current fix on the open 2.3.10 beta, and it looked absolutely bonkers.
Funnily, the previous "Elite+Dangerous+Fix+Beta+v1_2" and even the ancient "EDHorizonsv18.6-win7-64bit" worked considerably better and were at least bearable on the eyes.
Alright, thx Neph. Maybe I screwed up at some point. Will try again tomorrow.
EDIT: How embarrassing, I created my own archive of the Fix with a modified d3dx.ini, which was broken. Everything is indeed fine with the original version from Helix Mod. Sorry for the troubles.
Alright, thx Neph. Maybe I screwed up at some point. Will try again tomorrow.
EDIT: How embarrassing, I created my own archive of the Fix with a modified d3dx.ini, which was broken. Everything is indeed fine with the original version from Helix Mod. Sorry for the troubles.
Hey dude no problems I would rather get a report then nothing at all. At least we know it is still good for now..
Also I would try and disable shadows I have not fully tested to see if it was fixed but I do believe the shadows are broke again in the non beta probally broke in the beta as well ;)
Hey dude no problems I would rather get a report then nothing at all. At least we know it is still good for now..
Also I would try and disable shadows I have not fully tested to see if it was fixed but I do believe the shadows are broke again in the non beta probally broke in the beta as well ;)
Greetings guys. I've come across some other issue. After I did a completely clean re-installation of the original fix from the Helix Mod page, I've noticed massive flickering at some planet's rings. Since I haven't played the game for a long time, I can't really say if the update to 2.3.10 is the cause, but I think I have noticed it before the update.
However, I was able to trace it to "f0ea1824e905a278-ps_replace.txt". Once I removed that one the flickering was gone.
Regards,
zy.
Greetings guys. I've come across some other issue. After I did a completely clean re-installation of the original fix from the Helix Mod page, I've noticed massive flickering at some planet's rings. Since I haven't played the game for a long time, I can't really say if the update to 2.3.10 is the cause, but I think I have noticed it before the update.
However, I was able to trace it to "f0ea1824e905a278-ps_replace.txt". Once I removed that one the flickering was gone.
Sorry for the confusion. With "original fix" I meant the one found here: http://helixmod.blogspot.de/2016/09/elite-dangerous-sept-6-2016-update-by.html
As opposed to my own archive, which contained some minor modifications (mostly to d3dx.ini) for easy re-installation after updates or trying experimental stuff. I messed up the last backup however (by storing the ShaderCache instead of ShaderFixes *d'oh*) and had to go back to the last official version (Elite+Dangerous+v1.3+Beta+3D+Fix). That's when I started noticing the flickering.
Regards,
zy.
As opposed to my own archive, which contained some minor modifications (mostly to d3dx.ini) for easy re-installation after updates or trying experimental stuff. I messed up the last backup however (by storing the ShaderCache instead of ShaderFixes *d'oh*) and had to go back to the last official version (Elite+Dangerous+v1.3+Beta+3D+Fix). That's when I started noticing the flickering.
Yes that link was updated in June are you using that version the version numbers remain the same I go by the dates now.. so make sure it was dated in June, I will start updating the INI file with the current date..
Yes that link was updated in June are you using that version the version numbers remain the same I go by the dates now.. so make sure it was dated in June, I will start updating the INI file with the current date..
That clears some things up. :)
Latest file modification in the version I use is dated June 12th. However please make it so that every - even so little change - is reflected directly in the archive name, and not just in the ini. Maybe even consider uploading to github. Versioning is THE most important thing when it comes to tracking down bugs and issues.
Regards,
zy.
Latest file modification in the version I use is dated June 12th. However please make it so that every - even so little change - is reflected directly in the archive name, and not just in the ini. Maybe even consider uploading to github. Versioning is THE most important thing when it comes to tracking down bugs and issues.
Yes I realise that versioning is important but the guy who made the update program for 3D vision requested we keep the file names the same when we upload them..
I guess I could keep the file name the same just set the version number inside the ini file thnx .;)
Yes I realise that versioning is important but the guy who made the update program for 3D vision requested we keep the file names the same when we upload them..
I guess I could keep the file name the same just set the version number inside the ini file thnx .;)
Well, that's unfortunate. :)
For now, I'd just be happy if you keep the "Updated" date on the Helix-Page, well, up-to-date. So ppl know when something has changed. :)
However, I think the github thing would still be a good idea with this many ppl working on the project.
Actually, being a low level C(++) and asm dev myself, I've been thinking about getting into shaderfixing (which I currently know exactly "jack" about). Apart from being very busy atm, there would be absolutely no way I would even think about starting to work on a potentially outdated projectbase.
Regards,
zy.
Well, that's unfortunate. :)
For now, I'd just be happy if you keep the "Updated" date on the Helix-Page, well, up-to-date. So ppl know when something has changed. :)
However, I think the github thing would still be a good idea with this many ppl working on the project.
Actually, being a low level C(++) and asm dev myself, I've been thinking about getting into shaderfixing (which I currently know exactly "jack" about). Apart from being very busy atm, there would be absolutely no way I would even think about starting to work on a potentially outdated projectbase.
Well I took note of keeping the Updated date Updated ;)
I will try and remeber that.. Also well if you know that stuff this should be a breeze for you. you would probally intime be able to make some really nice fixes..
Well I took note of keeping the Updated date Updated ;)
I will try and remeber that.. Also well if you know that stuff this should be a breeze for you. you would probally intime be able to make some really nice fixes..
Note the one eye effect asteroid shadows appear there in one eye and gone in the other.. I looked at it but have no idea how to repair that issue.. I did try the flag in the ini it did not fix it..
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
I may disable them for now but I think we have the option to turn them off in options..
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
Funnily, the previous "Elite+Dangerous+Fix+Beta+v1_2" and even the ancient "EDHorizonsv18.6-win7-64bit" worked considerably better and were at least bearable on the eyes.
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
EDIT: How embarrassing, I created my own archive of the Fix with a modified d3dx.ini, which was broken. Everything is indeed fine with the original version from Helix Mod. Sorry for the troubles.
Also I would try and disable shadows I have not fully tested to see if it was fixed but I do believe the shadows are broke again in the non beta probally broke in the beta as well ;)
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
However, I was able to trace it to "f0ea1824e905a278-ps_replace.txt". Once I removed that one the flickering was gone.
Regards,
zy.
http://helixmod.blogspot.com/2016/01/elite-dangerous.html
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
As opposed to my own archive, which contained some minor modifications (mostly to d3dx.ini) for easy re-installation after updates or trying experimental stuff. I messed up the last backup however (by storing the ShaderCache instead of ShaderFixes *d'oh*) and had to go back to the last official version (Elite+Dangerous+v1.3+Beta+3D+Fix). That's when I started noticing the flickering.
Regards,
zy.
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
Latest file modification in the version I use is dated June 12th. However please make it so that every - even so little change - is reflected directly in the archive name, and not just in the ini. Maybe even consider uploading to github. Versioning is THE most important thing when it comes to tracking down bugs and issues.
Regards,
zy.
I guess I could keep the file name the same just set the version number inside the ini file thnx .;)
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit
For now, I'd just be happy if you keep the "Updated" date on the Helix-Page, well, up-to-date. So ppl know when something has changed. :)
However, I think the github thing would still be a good idea with this many ppl working on the project.
Actually, being a low level C(++) and asm dev myself, I've been thinking about getting into shaderfixing (which I currently know exactly "jack" about). Apart from being very busy atm, there would be absolutely no way I would even think about starting to work on a potentially outdated projectbase.
Regards,
zy.
I will try and remeber that.. Also well if you know that stuff this should be a breeze for you. you would probally intime be able to make some really nice fixes..
Intel i5 7600K @ 4.8ghz / MSI Z270 SLI / Asus 1080GTX - 416.16 / Optoma HD142x Projector / 1 4'x10' Curved Screen PVC / TrackIR / HOTAS Cougar / Cougar MFD's / Track IR / NVidia 3D Vision / Win 10 64bit