Increasing available depth? Registry tweak no longer available for Acer H5360 in 1.38
1 / 2
Hi- After every new 3d Vision driver installation, I used to decrease the "monitorsize" registry key to increase the depth effect on my Acer H5360. After upgrading to the latest 1.38 drivers, this setting is no longer available.
Hi- After every new 3d Vision driver installation, I used to decrease the "monitorsize" registry key to increase the depth effect on my Acer H5360. After upgrading to the latest 1.38 drivers, this setting is no longer available.
Hi- After every new 3d Vision driver installation, I used to decrease the "monitorsize" registry key to increase the depth effect on my Acer H5360. After upgrading to the latest 1.38 drivers, this setting is no longer available.
Hi- After every new 3d Vision driver installation, I used to decrease the "monitorsize" registry key to increase the depth effect on my Acer H5360. After upgrading to the latest 1.38 drivers, this setting is no longer available.
I´m also still waiting a Nvidia fix for h5360. I have 2233rz and h5360 and with the same deph I notice a BIG difference... I usually play with 50-60% with 2233rz, and when using h5360 I must move to 100% and still is not enough. But what I explain..., Nvidia know it perfectly.
Sometimes I think there are only ONE man working with the driver in the whole Nvidia company, and he must "work" only a weekend per month to add a few profiles and I don´t know what more. Some clear problems like this one is present for months and no fix... and must be something very very easy and quick. If Nvidia fix it I must be eternally grateful?
I´m also still waiting a Nvidia fix for h5360. I have 2233rz and h5360 and with the same deph I notice a BIG difference... I usually play with 50-60% with 2233rz, and when using h5360 I must move to 100% and still is not enough. But what I explain..., Nvidia know it perfectly.
Sometimes I think there are only ONE man working with the driver in the whole Nvidia company, and he must "work" only a weekend per month to add a few profiles and I don´t know what more. Some clear problems like this one is present for months and no fix... and must be something very very easy and quick. If Nvidia fix it I must be eternally grateful?
I´m also still waiting a Nvidia fix for h5360. I have 2233rz and h5360 and with the same deph I notice a BIG difference... I usually play with 50-60% with 2233rz, and when using h5360 I must move to 100% and still is not enough. But what I explain..., Nvidia know it perfectly.
Sometimes I think there are only ONE man working with the driver in the whole Nvidia company, and he must "work" only a weekend per month to add a few profiles and I don´t know what more. Some clear problems like this one is present for months and no fix... and must be something very very easy and quick. If Nvidia fix it I must be eternally grateful?
I´m also still waiting a Nvidia fix for h5360. I have 2233rz and h5360 and with the same deph I notice a BIG difference... I usually play with 50-60% with 2233rz, and when using h5360 I must move to 100% and still is not enough. But what I explain..., Nvidia know it perfectly.
Sometimes I think there are only ONE man working with the driver in the whole Nvidia company, and he must "work" only a weekend per month to add a few profiles and I don´t know what more. Some clear problems like this one is present for months and no fix... and must be something very very easy and quick. If Nvidia fix it I must be eternally grateful?
[quote name='tritosine' date='14 November 2010 - 09:47 PM' timestamp='1289771276' post='1146551']
my depth.bat works well.
messing in registry by hand can be tiresome no ? :D
do you have 32 or 64bit win?
Oh I see I have 1.37.
Bad news!
[/quote]
64-bit Windows. Yeah, the .bat changes the same value that I'm doing by hand. It's just not available anymore in 1.38.
C'mon, nvidia. Setting a static screen size for those of us using projectors is just lazy engineering given that some of us run 45" screens, while others run up to 200". At the very least, bring this registry key back.
[quote name='tritosine' date='14 November 2010 - 09:47 PM' timestamp='1289771276' post='1146551']
my depth.bat works well.
messing in registry by hand can be tiresome no ? :D
do you have 32 or 64bit win?
Oh I see I have 1.37.
Bad news!
64-bit Windows. Yeah, the .bat changes the same value that I'm doing by hand. It's just not available anymore in 1.38.
C'mon, nvidia. Setting a static screen size for those of us using projectors is just lazy engineering given that some of us run 45" screens, while others run up to 200". At the very least, bring this registry key back.
[quote name='tritosine' date='14 November 2010 - 09:47 PM' timestamp='1289771276' post='1146551']
my depth.bat works well.
messing in registry by hand can be tiresome no ? :D
do you have 32 or 64bit win?
Oh I see I have 1.37.
Bad news!
[/quote]
64-bit Windows. Yeah, the .bat changes the same value that I'm doing by hand. It's just not available anymore in 1.38.
C'mon, nvidia. Setting a static screen size for those of us using projectors is just lazy engineering given that some of us run 45" screens, while others run up to 200". At the very least, bring this registry key back.
[quote name='tritosine' date='14 November 2010 - 09:47 PM' timestamp='1289771276' post='1146551']
my depth.bat works well.
messing in registry by hand can be tiresome no ? :D
do you have 32 or 64bit win?
Oh I see I have 1.37.
Bad news!
64-bit Windows. Yeah, the .bat changes the same value that I'm doing by hand. It's just not available anymore in 1.38.
C'mon, nvidia. Setting a static screen size for those of us using projectors is just lazy engineering given that some of us run 45" screens, while others run up to 200". At the very least, bring this registry key back.
That's really bad news. I updated to 1.38 a few days ago especially for CoD: Black Ops. The newest drivers are strongly recommended for CoD: Black Ops because they include a profile for the game.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
That's really bad news. I updated to 1.38 a few days ago especially for CoD: Black Ops. The newest drivers are strongly recommended for CoD: Black Ops because they include a profile for the game.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
That's really bad news. I updated to 1.38 a few days ago especially for CoD: Black Ops. The newest drivers are strongly recommended for CoD: Black Ops because they include a profile for the game.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
That's really bad news. I updated to 1.38 a few days ago especially for CoD: Black Ops. The newest drivers are strongly recommended for CoD: Black Ops because they include a profile for the game.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
[quote name='lohan' date='15 November 2010 - 09:55 AM' timestamp='1289814931' post='1146764']
That's really bad news. I updated to 1.38 a few days ago especially for CoD: Black Ops. The newest drivers are strongly recommended for CoD: Black Ops because they include a profile for the game.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
What will you do?
[/quote]
I don't play Black Ops, so I think I'm going to stick 1.38 for now. However, the depth effect on most games is noticeably worse.
I am really frustrated at this point with 3D Vision, and am thinking of switching to iz3d + x103 glasses at this point.
-Project64 emulator is STILL not supported. It worked under the old nvidia 3d driver, and works under iz3d. No word back from nvidia on this after years of complaints.
-Like I said above, Nvidia treats 35" projector screen depth the same as 200" projector screen depth. This profoundly doesn't make sense.
[quote name='lohan' date='15 November 2010 - 09:55 AM' timestamp='1289814931' post='1146764']
That's really bad news. I updated to 1.38 a few days ago especially for CoD: Black Ops. The newest drivers are strongly recommended for CoD: Black Ops because they include a profile for the game.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
What will you do?
I don't play Black Ops, so I think I'm going to stick 1.38 for now. However, the depth effect on most games is noticeably worse.
I am really frustrated at this point with 3D Vision, and am thinking of switching to iz3d + x103 glasses at this point.
-Project64 emulator is STILL not supported. It worked under the old nvidia 3d driver, and works under iz3d. No word back from nvidia on this after years of complaints.
-Like I said above, Nvidia treats 35" projector screen depth the same as 200" projector screen depth. This profoundly doesn't make sense.
[quote name='lohan' date='15 November 2010 - 09:55 AM' timestamp='1289814931' post='1146764']
That's really bad news. I updated to 1.38 a few days ago especially for CoD: Black Ops. The newest drivers are strongly recommended for CoD: Black Ops because they include a profile for the game.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
What will you do?
[/quote]
I don't play Black Ops, so I think I'm going to stick 1.38 for now. However, the depth effect on most games is noticeably worse.
I am really frustrated at this point with 3D Vision, and am thinking of switching to iz3d + x103 glasses at this point.
-Project64 emulator is STILL not supported. It worked under the old nvidia 3d driver, and works under iz3d. No word back from nvidia on this after years of complaints.
-Like I said above, Nvidia treats 35" projector screen depth the same as 200" projector screen depth. This profoundly doesn't make sense.
[quote name='lohan' date='15 November 2010 - 09:55 AM' timestamp='1289814931' post='1146764']
That's really bad news. I updated to 1.38 a few days ago especially for CoD: Black Ops. The newest drivers are strongly recommended for CoD: Black Ops because they include a profile for the game.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
What will you do?
I don't play Black Ops, so I think I'm going to stick 1.38 for now. However, the depth effect on most games is noticeably worse.
I am really frustrated at this point with 3D Vision, and am thinking of switching to iz3d + x103 glasses at this point.
-Project64 emulator is STILL not supported. It worked under the old nvidia 3d driver, and works under iz3d. No word back from nvidia on this after years of complaints.
-Like I said above, Nvidia treats 35" projector screen depth the same as 200" projector screen depth. This profoundly doesn't make sense.
Could you please specify what exactly doesn't work anymore with 1.38. Is it that you can't do the manual registry thing (because you are stuck at some specific point)or can you still do the full routine but it seems the decreased screen size doesn't add more depth anymore?
I ask because I also upgraded to 1.38 especially for CoD:BO and I still can do the manual registry routine as I always did (run the game, switch to Windows while still running the game, enter the registry, decrease the screen size and switch back to the game) After I did the routine and switched back to the game I even switched back to Windows one more time to see if my changes are still active and still the given monitor size was the one that I entered manually before.
So if you tell me that you can still do the full registry routine but it just doesn't have an effect on the depth than yes, it seems it's not working anymore. But if you tell me you even can't do the routine anymore because you get stuck at some point than I would have to disagree because I can do the routine as I always did......
Could you please specify what exactly doesn't work anymore with 1.38. Is it that you can't do the manual registry thing (because you are stuck at some specific point)or can you still do the full routine but it seems the decreased screen size doesn't add more depth anymore?
I ask because I also upgraded to 1.38 especially for CoD:BO and I still can do the manual registry routine as I always did (run the game, switch to Windows while still running the game, enter the registry, decrease the screen size and switch back to the game) After I did the routine and switched back to the game I even switched back to Windows one more time to see if my changes are still active and still the given monitor size was the one that I entered manually before.
So if you tell me that you can still do the full registry routine but it just doesn't have an effect on the depth than yes, it seems it's not working anymore. But if you tell me you even can't do the routine anymore because you get stuck at some point than I would have to disagree because I can do the routine as I always did......
Could you please specify what exactly doesn't work anymore with 1.38. Is it that you can't do the manual registry thing (because you are stuck at some specific point)or can you still do the full routine but it seems the decreased screen size doesn't add more depth anymore?
I ask because I also upgraded to 1.38 especially for CoD:BO and I still can do the manual registry routine as I always did (run the game, switch to Windows while still running the game, enter the registry, decrease the screen size and switch back to the game) After I did the routine and switched back to the game I even switched back to Windows one more time to see if my changes are still active and still the given monitor size was the one that I entered manually before.
So if you tell me that you can still do the full registry routine but it just doesn't have an effect on the depth than yes, it seems it's not working anymore. But if you tell me you even can't do the routine anymore because you get stuck at some point than I would have to disagree because I can do the routine as I always did......
Could you please specify what exactly doesn't work anymore with 1.38. Is it that you can't do the manual registry thing (because you are stuck at some specific point)or can you still do the full routine but it seems the decreased screen size doesn't add more depth anymore?
I ask because I also upgraded to 1.38 especially for CoD:BO and I still can do the manual registry routine as I always did (run the game, switch to Windows while still running the game, enter the registry, decrease the screen size and switch back to the game) After I did the routine and switched back to the game I even switched back to Windows one more time to see if my changes are still active and still the given monitor size was the one that I entered manually before.
So if you tell me that you can still do the full registry routine but it just doesn't have an effect on the depth than yes, it seems it's not working anymore. But if you tell me you even can't do the routine anymore because you get stuck at some point than I would have to disagree because I can do the routine as I always did......
Wow! I just tried the depth hack for the first time and it worked perfectly. I'm using 260.99 (both the 3D Vision driver and the graphics driver) and have only tried the depth hack with GT Legends. It really does make a huge difference, as before I used to run it at 100% and wanted more depth. Now I have it at 20% and the depth is pretty much perfect.
I have a 60" Mitsubishi WD-60737 and sit about 6.5' away from the screen.
Wow! I just tried the depth hack for the first time and it worked perfectly. I'm using 260.99 (both the 3D Vision driver and the graphics driver) and have only tried the depth hack with GT Legends. It really does make a huge difference, as before I used to run it at 100% and wanted more depth. Now I have it at 20% and the depth is pretty much perfect.
I have a 60" Mitsubishi WD-60737 and sit about 6.5' away from the screen.
Anybody else see this? Any solutions?
Anybody else see this? Any solutions?
Anybody else see this? Any solutions?
Anybody else see this? Any solutions?
Sometimes I think there are only ONE man working with the driver in the whole Nvidia company, and he must "work" only a weekend per month to add a few profiles and I don´t know what more. Some clear problems like this one is present for months and no fix... and must be something very very easy and quick. If Nvidia fix it I must be eternally grateful?
Sometimes I think there are only ONE man working with the driver in the whole Nvidia company, and he must "work" only a weekend per month to add a few profiles and I don´t know what more. Some clear problems like this one is present for months and no fix... and must be something very very easy and quick. If Nvidia fix it I must be eternally grateful?
- Windows 7 64bits (SSD OCZ-Vertez2 128Gb)
- "ASUS P6X58D-E" motherboard
- "MSI GTX 660 TI"
- "Intel Xeon X5670" @4000MHz CPU (20.0[12-25]x200MHz)
- RAM 16 Gb DDR3 1600
- "Dell S2716DG" monitor (2560x1440 @144Hz)
- "Corsair Carbide 600C" case
- Labrador dog (cinnamon edition)
Sometimes I think there are only ONE man working with the driver in the whole Nvidia company, and he must "work" only a weekend per month to add a few profiles and I don´t know what more. Some clear problems like this one is present for months and no fix... and must be something very very easy and quick. If Nvidia fix it I must be eternally grateful?
Sometimes I think there are only ONE man working with the driver in the whole Nvidia company, and he must "work" only a weekend per month to add a few profiles and I don´t know what more. Some clear problems like this one is present for months and no fix... and must be something very very easy and quick. If Nvidia fix it I must be eternally grateful?
- Windows 7 64bits (SSD OCZ-Vertez2 128Gb)
- "ASUS P6X58D-E" motherboard
- "MSI GTX 660 TI"
- "Intel Xeon X5670" @4000MHz CPU (20.0[12-25]x200MHz)
- RAM 16 Gb DDR3 1600
- "Dell S2716DG" monitor (2560x1440 @144Hz)
- "Corsair Carbide 600C" case
- Labrador dog (cinnamon edition)
messing in registry by hand can be tiresome no ? :D
do you have 32 or 64bit win?
Oh I see I have 1.37.
Bad news!
messing in registry by hand can be tiresome no ? :D
do you have 32 or 64bit win?
Oh I see I have 1.37.
Bad news!
messing in registry by hand can be tiresome no ? :D
do you have 32 or 64bit win?
Oh I see I have 1.37.
Bad news!
messing in registry by hand can be tiresome no ? :D
do you have 32 or 64bit win?
Oh I see I have 1.37.
Bad news!
my depth.bat works well.
messing in registry by hand can be tiresome no ? :D
do you have 32 or 64bit win?
Oh I see I have 1.37.
Bad news!
[/quote]
64-bit Windows. Yeah, the .bat changes the same value that I'm doing by hand. It's just not available anymore in 1.38.
C'mon, nvidia. Setting a static screen size for those of us using projectors is just lazy engineering given that some of us run 45" screens, while others run up to 200". At the very least, bring this registry key back.
my depth.bat works well.
messing in registry by hand can be tiresome no ? :D
do you have 32 or 64bit win?
Oh I see I have 1.37.
Bad news!
64-bit Windows. Yeah, the .bat changes the same value that I'm doing by hand. It's just not available anymore in 1.38.
C'mon, nvidia. Setting a static screen size for those of us using projectors is just lazy engineering given that some of us run 45" screens, while others run up to 200". At the very least, bring this registry key back.
my depth.bat works well.
messing in registry by hand can be tiresome no ? :D
do you have 32 or 64bit win?
Oh I see I have 1.37.
Bad news!
[/quote]
64-bit Windows. Yeah, the .bat changes the same value that I'm doing by hand. It's just not available anymore in 1.38.
C'mon, nvidia. Setting a static screen size for those of us using projectors is just lazy engineering given that some of us run 45" screens, while others run up to 200". At the very least, bring this registry key back.
my depth.bat works well.
messing in registry by hand can be tiresome no ? :D
do you have 32 or 64bit win?
Oh I see I have 1.37.
Bad news!
64-bit Windows. Yeah, the .bat changes the same value that I'm doing by hand. It's just not available anymore in 1.38.
C'mon, nvidia. Setting a static screen size for those of us using projectors is just lazy engineering given that some of us run 45" screens, while others run up to 200". At the very least, bring this registry key back.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
What will you do?
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
What will you do?
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
What will you do?
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
What will you do?
That's really bad news. I updated to 1.38 a few days ago especially for CoD: Black Ops. The newest drivers are strongly recommended for CoD: Black Ops because they include a profile for the game.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
What will you do?
[/quote]
I don't play Black Ops, so I think I'm going to stick 1.38 for now. However, the depth effect on most games is noticeably worse.
I am really frustrated at this point with 3D Vision, and am thinking of switching to iz3d + x103 glasses at this point.
-Project64 emulator is STILL not supported. It worked under the old nvidia 3d driver, and works under iz3d. No word back from nvidia on this after years of complaints.
-Like I said above, Nvidia treats 35" projector screen depth the same as 200" projector screen depth. This profoundly doesn't make sense.
That's really bad news. I updated to 1.38 a few days ago especially for CoD: Black Ops. The newest drivers are strongly recommended for CoD: Black Ops because they include a profile for the game.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
What will you do?
I don't play Black Ops, so I think I'm going to stick 1.38 for now. However, the depth effect on most games is noticeably worse.
I am really frustrated at this point with 3D Vision, and am thinking of switching to iz3d + x103 glasses at this point.
-Project64 emulator is STILL not supported. It worked under the old nvidia 3d driver, and works under iz3d. No word back from nvidia on this after years of complaints.
-Like I said above, Nvidia treats 35" projector screen depth the same as 200" projector screen depth. This profoundly doesn't make sense.
That's really bad news. I updated to 1.38 a few days ago especially for CoD: Black Ops. The newest drivers are strongly recommended for CoD: Black Ops because they include a profile for the game.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
What will you do?
[/quote]
I don't play Black Ops, so I think I'm going to stick 1.38 for now. However, the depth effect on most games is noticeably worse.
I am really frustrated at this point with 3D Vision, and am thinking of switching to iz3d + x103 glasses at this point.
-Project64 emulator is STILL not supported. It worked under the old nvidia 3d driver, and works under iz3d. No word back from nvidia on this after years of complaints.
-Like I said above, Nvidia treats 35" projector screen depth the same as 200" projector screen depth. This profoundly doesn't make sense.
That's really bad news. I updated to 1.38 a few days ago especially for CoD: Black Ops. The newest drivers are strongly recommended for CoD: Black Ops because they include a profile for the game.
Should I go back to the older drivers so I can do the registry tweak again or should I stick to 1.38 because there are serious problems with one of the older drivers and CoD: Black Ops?
What will you do?
I don't play Black Ops, so I think I'm going to stick 1.38 for now. However, the depth effect on most games is noticeably worse.
I am really frustrated at this point with 3D Vision, and am thinking of switching to iz3d + x103 glasses at this point.
-Project64 emulator is STILL not supported. It worked under the old nvidia 3d driver, and works under iz3d. No word back from nvidia on this after years of complaints.
-Like I said above, Nvidia treats 35" projector screen depth the same as 200" projector screen depth. This profoundly doesn't make sense.
I ask because I also upgraded to 1.38 especially for CoD:BO and I still can do the manual registry routine as I always did (run the game, switch to Windows while still running the game, enter the registry, decrease the screen size and switch back to the game) After I did the routine and switched back to the game I even switched back to Windows one more time to see if my changes are still active and still the given monitor size was the one that I entered manually before.
So if you tell me that you can still do the full registry routine but it just doesn't have an effect on the depth than yes, it seems it's not working anymore. But if you tell me you even can't do the routine anymore because you get stuck at some point than I would have to disagree because I can do the routine as I always did......
I ask because I also upgraded to 1.38 especially for CoD:BO and I still can do the manual registry routine as I always did (run the game, switch to Windows while still running the game, enter the registry, decrease the screen size and switch back to the game) After I did the routine and switched back to the game I even switched back to Windows one more time to see if my changes are still active and still the given monitor size was the one that I entered manually before.
So if you tell me that you can still do the full registry routine but it just doesn't have an effect on the depth than yes, it seems it's not working anymore. But if you tell me you even can't do the routine anymore because you get stuck at some point than I would have to disagree because I can do the routine as I always did......
I ask because I also upgraded to 1.38 especially for CoD:BO and I still can do the manual registry routine as I always did (run the game, switch to Windows while still running the game, enter the registry, decrease the screen size and switch back to the game) After I did the routine and switched back to the game I even switched back to Windows one more time to see if my changes are still active and still the given monitor size was the one that I entered manually before.
So if you tell me that you can still do the full registry routine but it just doesn't have an effect on the depth than yes, it seems it's not working anymore. But if you tell me you even can't do the routine anymore because you get stuck at some point than I would have to disagree because I can do the routine as I always did......
I ask because I also upgraded to 1.38 especially for CoD:BO and I still can do the manual registry routine as I always did (run the game, switch to Windows while still running the game, enter the registry, decrease the screen size and switch back to the game) After I did the routine and switched back to the game I even switched back to Windows one more time to see if my changes are still active and still the given monitor size was the one that I entered manually before.
So if you tell me that you can still do the full registry routine but it just doesn't have an effect on the depth than yes, it seems it's not working anymore. But if you tell me you even can't do the routine anymore because you get stuck at some point than I would have to disagree because I can do the routine as I always did......
I have a 60" Mitsubishi WD-60737 and sit about 6.5' away from the screen.
I have a 60" Mitsubishi WD-60737 and sit about 6.5' away from the screen.