3D Fix Manager - Application for installing 3D Vision Fixes + Hotkey Editing Support
  53 / 60    
[quote="Pauldusler"][quote="NeIVIeSiS"]I have a feature request, if possible that might improve the software. I noticed we can turn on/off 3D Vision globally from it, instead of using the NVIDIA control panel. This is helpful. Is it possible to implement this feature on a per-game basis? The reason I ask is actually for Starcraft 2. While this game supports 3D and has its own settings, I prefer it in 2D due to its competitive nature. However, sometimes 3D fires on its own when I play the game in 2-D, while clicking CTRL+T is not a big deal normally, it is when you are in the middle of combat in a multiplayer RTS. I have 3D enabled globally for other games. So ideally, I could turn off 3D ONLY for specified games such as Starcraft 2 so 3D Vision would never fire. I would assume other games might fall in similar scenarios. Is this convenience possible?[/quote] Not sure if I understood you correctly. So you clicked on "Play 2D" button and played Starcraft II in 2D. Then suddenly while gaming 3D kicked in? I cannot remember that this ever happened to me in any game so far. When clicking on "Play 2D" button Stereoscopic 3D is completely turned off (same as turning 3D off in Nvidia Control Panel).[/quote] Your software works as intended. If I use the current toggle, it will either enable 3D Vision globally or disable it globally for all games. Just as if I was to do it through the Nvidia Driver. But that's not what I described. What I think might be a nice-to-have, is a toggle that is game specific. In other words, keep the global toggle. But also each game profile can have its own 3D Vision on/off to not have to do it manually in-game with CTRL+T. And this might seem silly, but the reason I bring it up is that some games turn on 3d Vision on their own randomly sometimes (such as Starcraft 2). This means I have to toggle it inside the game by doing the Control+T whenever this happens, but it's annoying as it can randomly happen several times in a gaming session.
Pauldusler said:
NeIVIeSiS said:I have a feature request, if possible that might improve the software.

I noticed we can turn on/off 3D Vision globally from it, instead of using the NVIDIA control panel. This is helpful. Is it possible to implement this feature on a per-game basis?

The reason I ask is actually for Starcraft 2. While this game supports 3D and has its own settings, I prefer it in 2D due to its competitive nature. However, sometimes 3D fires on its own when I play the game in 2-D, while clicking CTRL+T is not a big deal normally, it is when you are in the middle of combat in a multiplayer RTS.

I have 3D enabled globally for other games. So ideally, I could turn off 3D ONLY for specified games such as Starcraft 2 so 3D Vision would never fire. I would assume other games might fall in similar scenarios.

Is this convenience possible?


Not sure if I understood you correctly. So you clicked on "Play 2D" button and played Starcraft II in 2D. Then suddenly while gaming 3D kicked in? I cannot remember that this ever happened to me in any game so far. When clicking on "Play 2D" button Stereoscopic 3D is completely turned off (same as turning 3D off in Nvidia Control Panel).


Your software works as intended. If I use the current toggle, it will either enable 3D Vision globally or disable it globally for all games. Just as if I was to do it through the Nvidia Driver.

But that's not what I described. What I think might be a nice-to-have, is a toggle that is game specific. In other words, keep the global toggle. But also each game profile can have its own 3D Vision on/off to not have to do it manually in-game with CTRL+T.

And this might seem silly, but the reason I bring it up is that some games turn on 3d Vision on their own randomly sometimes (such as Starcraft 2). This means I have to toggle it inside the game by doing the Control+T whenever this happens, but it's annoying as it can randomly happen several times in a gaming session.

CPU: Intel Core i7 3770K @ 3.50GHz
MB: Asus P8Z77-V DELUXE
RAM: 32.0GB Dual-Channel DDR3 @ 799MHz (10-10-10-27)
VGA: Asus Strix GTX 1070 2x SLI
DISPLAY: Asus ROG PG278QR
OS: Windows 10 Home 64-bit

Posted 12/04/2018 07:57 PM   
[quote="Helifax"] That seems to have worked;) Which is wonderful! I played a bit with it and I couldn't find a problem. I guess you can safely push it to the main release branch! As for the other topic, I am using Windows 10 x64 Pro and Home (on Desktop and Laptop). I still have a win7 partition that I haven't booted in years now:)) PS: Forgot to mention something important! Thank you very much for taking the time and looking into this![/quote] You're welcome. For the other issue I'll just make IR output modes optional - that means you have to tick a checkbox first to change / force different modes. I think that will solve this. [quote="NeIVIeSiS"] Your software works as intended. If I use the current toggle, it will either enable 3D Vision globally or disable it globally for all games. Just as if I was to do it through the Nvidia Driver. But that's not what I described. What I think might be a nice-to-have, is a toggle that is game specific. In other words, keep the global toggle. But also each game profile can have its own 3D Vision on/off to not have to do it manually in-game with CTRL+T. And this might seem silly, but the reason I bring it up is that some games turn on 3d Vision on their own randomly sometimes (such as Starcraft 2). This means I have to toggle it inside the game by doing the Control+T whenever this happens, but it's annoying as it can randomly happen several times in a gaming session. [/quote] Ah you mean that stereoscopic effects shall be individually hidden / shown on game launch when clicking on "Play 3D" button? So far there is indeed only a global switch for controlling this in "Nvidia 3D Settings" tab. Its name is "3D mode enabled on game launch". Would be no problem to make this game specific by adding an option in the fix profile. But I don't know if this would solve your issue you described about 3D kicking in randomly while gaming. Most reliable way would be to just start the game by clicking on the "Play 2D" button. This reliably turns off 3D and it has no chance for randomly activating while gaming. The Play 2D / Play 3D buttons are like game specific toggles for this.
Helifax said:

That seems to have worked;) Which is wonderful! I played a bit with it and I couldn't find a problem. I guess you can safely push it to the main release branch!

As for the other topic, I am using Windows 10 x64 Pro and Home (on Desktop and Laptop). I still have a win7 partition that I haven't booted in years now:))

PS:
Forgot to mention something important! Thank you very much for taking the time and looking into this!


You're welcome. For the other issue I'll just make IR output modes optional - that means you have to tick a checkbox first to change / force different modes. I think that will solve this.

NeIVIeSiS said:
Your software works as intended. If I use the current toggle, it will either enable 3D Vision globally or disable it globally for all games. Just as if I was to do it through the Nvidia Driver.

But that's not what I described. What I think might be a nice-to-have, is a toggle that is game specific. In other words, keep the global toggle. But also each game profile can have its own 3D Vision on/off to not have to do it manually in-game with CTRL+T.

And this might seem silly, but the reason I bring it up is that some games turn on 3d Vision on their own randomly sometimes (such as Starcraft 2). This means I have to toggle it inside the game by doing the Control+T whenever this happens, but it's annoying as it can randomly happen several times in a gaming session.



Ah you mean that stereoscopic effects shall be individually hidden / shown on game launch when clicking on "Play 3D" button? So far there is indeed only a global switch for controlling this in "Nvidia 3D Settings" tab. Its name is "3D mode enabled on game launch". Would be no problem to make this game specific by adding an option in the fix profile. But I don't know if this would solve your issue you described about 3D kicking in randomly while gaming. Most reliable way would be to just start the game by clicking on the "Play 2D" button. This reliably turns off 3D and it has no chance for randomly activating while gaming. The Play 2D / Play 3D buttons are like game specific toggles for this.

ASUS ROG Strix GeForce GTX 1080 | Core I7-7700K | 16GB RAM | Win10 Pro x64
Asus ROG Swift PG278Q 3D Vision Monitor
Optoma UHD 40 3D Vision Projector
Paypal donations for 3D Fix Manager: duselpaul86@gmx.de

Posted 12/04/2018 11:35 PM   
@ Helifax and rustyk21: Ok I've changed that IR output thing. The registry entries envolved in this aren't set by default any more when doing a quick 3D vision setup or when applying settings in Nvidia 3D Settings tab. IR output mode can be still set if the checkbox is enabled manually (by default this is set of "Off"). For me this doesn't break synchronisation between pyramid and glasses but obviously it does not work for all PC configurations... I still was not able to reproduce the Steam uninstall message. My guess is that some games use different Steam app IDs for different countries. Maybe the Steam APP ID doesn't match to your country but that's just a wild guess. A temporary fix would be to start all games via the game exe. You can set this globally in 3DFM if a game shall be generally launched via Steam app id or game exe. However when launching a game directly over exe some games don't upload the savegames then to the Steam cloud. @rustyk21 Which divinity game is it which had the issue? We have 5 different divinity games on helixblog which are all 3D fixed... I'll release the new version of 3DFM soon.
@ Helifax and rustyk21:

Ok I've changed that IR output thing. The registry entries envolved in this aren't set by default any more when doing a quick 3D vision setup or when applying settings in Nvidia 3D Settings tab. IR output mode can be still set if the checkbox is enabled manually (by default this is set of "Off"). For me this doesn't break synchronisation between pyramid and glasses but obviously it does not work for all PC configurations...

I still was not able to reproduce the Steam uninstall message. My guess is that some games use different Steam app IDs for different countries. Maybe the Steam APP ID doesn't match to your country but that's just a wild guess. A temporary fix would be to start all games via the game exe. You can set this globally in 3DFM if a game shall be generally launched via Steam app id or game exe. However when launching a game directly over exe some games don't upload the savegames then to the Steam cloud.

@rustyk21 Which divinity game is it which had the issue? We have 5 different divinity games on helixblog which are all 3D fixed...

I'll release the new version of 3DFM soon.

ASUS ROG Strix GeForce GTX 1080 | Core I7-7700K | 16GB RAM | Win10 Pro x64
Asus ROG Swift PG278Q 3D Vision Monitor
Optoma UHD 40 3D Vision Projector
Paypal donations for 3D Fix Manager: duselpaul86@gmx.de

Posted 12/05/2018 03:57 PM   
Hi Markus, after making the adjustment on Nvidia 3D Settings tab, 3d glasses stopped working.( glasses will not sync with the emitter.) First, I thought the battery was exhausted. I did research on how to change the battery for a week :( a week later i uninstalled driver and tried again install. 3D glasses sync problem fixed . The first time I encountered such a problem. I never thought the problem was caused by "3D Fix Manager". Because i haven't used 3D Fix Manager's "Nvidia 3D Settings tab" for a long time. [quote="Pauldusler"] Could one of you please create 2 screenshots of your Windows registry settings in "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\NVIDIA Corporation\Global\Stereo3D" and post it here? One screenshot of the Registry settings before you clicked on "Apply" button in 3D Fix Manager (when everything still works) and one screenshot after you clicked on it (and 3D Vision is broken after that).[/quote] [color="orange"][b] Everything still works[/b][/color] [img] https://forums.geforce.com/cmd/default/download-comment-attachment/76607/[/img] [color="orange"][b]3D Vision is broken after that[/b][/color] [img] https://forums.geforce.com/cmd/default/download-comment-attachment/76608/[/img] [img] https://forums.geforce.com/cmd/default/download-comment-attachment/76606/[/img]
Hi Markus, after making the adjustment on Nvidia 3D Settings tab, 3d glasses stopped working.( glasses will not sync with the emitter.) First, I thought the battery was exhausted. I did research on how to change the battery for a week :( a week later i uninstalled driver and tried again install. 3D glasses sync problem fixed . The first time I encountered such a problem. I never thought the problem was caused by "3D Fix Manager". Because i haven't used 3D Fix Manager's "Nvidia 3D Settings tab" for a long time.


Pauldusler said:
Could one of you please create 2 screenshots of your Windows registry settings in "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\NVIDIA Corporation\Global\Stereo3D" and post it here? One screenshot of the Registry settings before you clicked on "Apply" button in 3D Fix Manager (when everything still works) and one screenshot after you clicked on it (and 3D Vision is broken after that).

Everything still works
Image

3D Vision is broken after that
Image
Image

Windows 10 Pro x64 (1809) / Intel i7 6700K 4.7GHz (Corsair H110) / Gigabyte GA-Z170X-UD5 TH (Bios F21) / Corsair Vengeance 32GB DDR4 3000MHz / Gigabyte GTX 1080Ti Xtreme WaterForce + SLI / Sound Blaster Z / Samsung 950 Pro NVMe (512GB) / EVGA SuperNOVA 1000W 80+ Platinum 220V / Asus Rog Swift PG278Q / 3D Kit 3D Vision 2 / Nvidia Shield TV (2017)
Battlefront 3D Fix Geek Version
Check out my 3D Videos & Screenshots / Youtube video downloader (8K )

Posted 12/05/2018 07:51 PM   
Hi Tim, thank you very much for creating those screenshots. I could reproduce the issue now thanks to your screenshots. When both StereoIROutput and StereoFlywheelCycleState are set to 0 the synchronisation doesn't work any more. I'm very surprised why both of them are set to 0 because in the source code this combination does not exist. My best guess is that the ValueConverter I've written crashes for unknown reasons and the value for both registry entries are set to 0 therefore. These are the possible combinations for the registry entries: [u]Single IR:[/u] StereoIROutput = 3 StereoFlywheelCycleState = 0 [u]Multi IR:[/u] StereoIROutput = 3 StereoFlywheelCycleState = 1 [u]LAN Environment:[/u] StereoIROutput = 1 StereoFlywheelCycleState = 0 As said I'm not sure yet why both entries were set to 0 but I've changed the code today. The value converter isn't used any more and changing IR output mode is optional for the next 3DFM version. I think it was 99% the value converter because it wasn't even capsulated in a try catch block ^^. I'm very sorry that you couldn't use 3D Vision a few days due to this. I hope you didn't order new glasses ;D. Thx for your help figuring this out. I experimented with random numbers for StereoIROutput and StereoFlywheelCycleState yesterday but I didn't have the idea to set both of them to 0. Now things are clear what caused the issue. EDIT: it seems like as soon as StereoIROutput is set to 0 synchronization doesn't work any more no matter what is set for StereoFlywheelCycleState.
Hi Tim,

thank you very much for creating those screenshots. I could reproduce the issue now thanks to your screenshots. When both StereoIROutput and StereoFlywheelCycleState are set to 0 the synchronisation doesn't work any more. I'm very surprised why both of them are set to 0 because in the source code this combination does not exist. My best guess is that the ValueConverter I've written crashes for unknown reasons and the value for both registry entries are set to 0 therefore.

These are the possible combinations for the registry entries:

Single IR:
StereoIROutput = 3
StereoFlywheelCycleState = 0

Multi IR:
StereoIROutput = 3
StereoFlywheelCycleState = 1

LAN Environment:
StereoIROutput = 1
StereoFlywheelCycleState = 0

As said I'm not sure yet why both entries were set to 0 but I've changed the code today. The value converter isn't used any more and changing IR output mode is optional for the next 3DFM version. I think it was 99% the value converter because it wasn't even capsulated in a try catch block ^^.

I'm very sorry that you couldn't use 3D Vision a few days due to this. I hope you didn't order new glasses ;D. Thx for your help figuring this out. I experimented with random numbers for StereoIROutput and StereoFlywheelCycleState yesterday but I didn't have the idea to set both of them to 0. Now things are clear what caused the issue.

EDIT: it seems like as soon as StereoIROutput is set to 0 synchronization doesn't work any more no matter what is set for StereoFlywheelCycleState.

ASUS ROG Strix GeForce GTX 1080 | Core I7-7700K | 16GB RAM | Win10 Pro x64
Asus ROG Swift PG278Q 3D Vision Monitor
Optoma UHD 40 3D Vision Projector
Paypal donations for 3D Fix Manager: duselpaul86@gmx.de

Posted 12/05/2018 09:02 PM   
Good team work :-) @Pauldusler, it was Divinity Original Sin Enhanced edition that exhibited the behaivour of appearing to be uninstalled. I wouldn't worry about it until I manage to recreate the steps reliably, it's probably a better use of your time to concentrate on other things :-)
Good team work :-)

@Pauldusler, it was Divinity Original Sin Enhanced edition that exhibited the behaivour of appearing to be uninstalled. I wouldn't worry about it until I manage to recreate the steps reliably, it's probably a better use of your time to concentrate on other things :-)

Gigabyte RTX2080TI Gaming OC, I7-6700k ~ 4.4Ghz, 3x BenQ XL2420T, BenQ TK800, LG 55EG960V (3D OLED), Samsung 850 EVO SSD, Crucial M4 SSD, 3D vision kit, Xpand x104 glasses, Corsair HX1000i, Win 10 pro 64/Win 7 64https://www.3dmark.com/fs/9529310

Posted 12/05/2018 10:11 PM   
[quote="Pauldusler"]I'm very sorry that you couldn't use 3D Vision a few days due to this. I hope you didn't order new glasses ;D. Thx for your help figuring this out. [/quote]I didn't buy glasses. But i thought about buying. :D I'm glad you can detect the problem.
Pauldusler said:I'm very sorry that you couldn't use 3D Vision a few days due to this. I hope you didn't order new glasses ;D. Thx for your help figuring this out.
I didn't buy glasses. But i thought about buying. :D
I'm glad you can detect the problem.

Windows 10 Pro x64 (1809) / Intel i7 6700K 4.7GHz (Corsair H110) / Gigabyte GA-Z170X-UD5 TH (Bios F21) / Corsair Vengeance 32GB DDR4 3000MHz / Gigabyte GTX 1080Ti Xtreme WaterForce + SLI / Sound Blaster Z / Samsung 950 Pro NVMe (512GB) / EVGA SuperNOVA 1000W 80+ Platinum 220V / Asus Rog Swift PG278Q / 3D Kit 3D Vision 2 / Nvidia Shield TV (2017)
Battlefront 3D Fix Geek Version
Check out my 3D Videos & Screenshots / Youtube video downloader (8K )

Posted 12/06/2018 05:10 AM   
[quote="TimFx7"][quote="Pauldusler"]I'm very sorry that you couldn't use 3D Vision a few days due to this. I hope you didn't order new glasses ;D. Thx for your help figuring this out. [/quote]I didn't buy glasses. But i thought about buying. :D I'm glad you can detect the problem. [/quote] In the meantime I've found the reason for the issue in the source code. It wasn't the value converter. After installing a driver update both registry entries (StereoIROutput and StereoFlywheelCycleState) do not exist any more. Your screenshots prove this. 3DFM tries to find them in the Registry but fails of course. For weird reasons I've defined that in this case just a 0 value is returned then instead of the driver default value. I will generally change this to return the driver default values instead of just 0. So and why wasn't emitter synchronization broken for me? Because after a driver update I loaded my XML settings file which corrected this error. Or I changed "Single IR" to "Lan environment" in Nvidia 3D Settings tab and clicked on "Apply" and this also corrected it. My emitter somehow only works correctly in "Lan Environment" or "Multiple IR". But still I don't know why a "Quick Setup" (skipping the 3D Vision setup wizard) breaks the synchronization for Helifax. Because in this case the default values of StereoIROutput and StereoFlywheelCycleState (3 and 0) are loaded and these values are written to the Registry then. Maybe Helifax loaded a XML settings file afterwards then where the values were broken or so. Not clear why that issue happened. But for safety reason I'll keep the changes I did yesterday that both of the registry entries aren't changed any more by default. Btw I'll release the new version today. Just want to implement 2 minor things more on my to do list then version 1.64 is completed.
TimFx7 said:
Pauldusler said:I'm very sorry that you couldn't use 3D Vision a few days due to this. I hope you didn't order new glasses ;D. Thx for your help figuring this out.
I didn't buy glasses. But i thought about buying. :D
I'm glad you can detect the problem.



In the meantime I've found the reason for the issue in the source code. It wasn't the value converter. After installing a driver update both registry entries (StereoIROutput and StereoFlywheelCycleState) do not exist any more. Your screenshots prove this. 3DFM tries to find them in the Registry but fails of course. For weird reasons I've defined that in this case just a 0 value is returned then instead of the driver default value. I will generally change this to return the driver default values instead of just 0.

So and why wasn't emitter synchronization broken for me? Because after a driver update I loaded my XML settings file which corrected this error. Or I changed "Single IR" to "Lan environment" in Nvidia 3D Settings tab and clicked on "Apply" and this also corrected it. My emitter somehow only works correctly in "Lan Environment" or "Multiple IR".

But still I don't know why a "Quick Setup" (skipping the 3D Vision setup wizard) breaks the synchronization for Helifax. Because in this case the default values of StereoIROutput and StereoFlywheelCycleState (3 and 0) are loaded and these values are written to the Registry then. Maybe Helifax loaded a XML settings file afterwards then where the values were broken or so. Not clear why that issue happened. But for safety reason I'll keep the changes I did yesterday that both of the registry entries aren't changed any more by default.

Btw I'll release the new version today. Just want to implement 2 minor things more on my to do list then version 1.64 is completed.

ASUS ROG Strix GeForce GTX 1080 | Core I7-7700K | 16GB RAM | Win10 Pro x64
Asus ROG Swift PG278Q 3D Vision Monitor
Optoma UHD 40 3D Vision Projector
Paypal donations for 3D Fix Manager: duselpaul86@gmx.de

Posted 12/06/2018 08:03 AM   
I forgot to mention an important point . I'm doing quick setup in every driver installation. ( Advanced 3D Vision Configuration 1.4 ) I'm loading the settings from an xml file. (skipping the 3D Vision setup wizard) I've been using this way for 3 years. Although 3D running smoothly, xml file "StereoIROutput and StereoFlywheelCycleState" do not have these values. I probably would not be a problem on 3DFM if I had used 3D Vision setup wizard.
I forgot to mention an important point . I'm doing quick setup in every driver installation. ( Advanced 3D Vision Configuration 1.4 ) I'm loading the settings from an xml file. (skipping the 3D Vision setup wizard)
I've been using this way for 3 years. Although 3D running smoothly, xml file "StereoIROutput and StereoFlywheelCycleState" do not have these values. I probably would not be a problem on 3DFM if I had used 3D Vision setup wizard.

Windows 10 Pro x64 (1809) / Intel i7 6700K 4.7GHz (Corsair H110) / Gigabyte GA-Z170X-UD5 TH (Bios F21) / Corsair Vengeance 32GB DDR4 3000MHz / Gigabyte GTX 1080Ti Xtreme WaterForce + SLI / Sound Blaster Z / Samsung 950 Pro NVMe (512GB) / EVGA SuperNOVA 1000W 80+ Platinum 220V / Asus Rog Swift PG278Q / 3D Kit 3D Vision 2 / Nvidia Shield TV (2017)
Battlefront 3D Fix Geek Version
Check out my 3D Videos & Screenshots / Youtube video downloader (8K )

Posted 12/06/2018 11:31 AM   
[color="orange"]Version 1.64 released[/color] Change notes: [list] [.]New: Supported resolutions and refresh rates of the primary display are automatically detected. To enable this feature go to "Display Profiles" tab and link your display to your desired display profile.[/.] [.]New: Supported resolutions are cached in a file for faster accessing this information[/.] [.]New: When updating all installed 3dmigoto wrappers the dialog window tells you how many games have been updated.[/.] [.]Changed: By default IR output mode isn't changed any more when applying settings in "Nvidia 3D Settings" tab or when skipping 3D Vision setup wizard. For changing IR mode you have to manually tick the option "Sync mode of IR Sender" in "Nvidia 3D Settings" tab first.[/.] [.]Changed: Search text for filtering games doesn't need to be so precise any more. So for example it doesn't matter if you type in "Assassin's Creed" or "assassinscreed" for listing all AC games.[/.] [.]Changed: Updated 3dmigoto files to version 1.3.12[/.] [.]Changed: Reworked some tooltips in "Hotkeys" tab[/.] [.]Bugfix: Synchronization between glasses and IR emitter could break when applying settings in "Nvidia 3D Settings" tab[/.] [.]Bugfix: "Delay" option in "Hotkeys" tab wasn't shown for 3dmigoto fixes when key type was either set to "cycle" or "toggle"[/.] [.]Bugfix: "Release Transition" option in "Hotkeys" tab wasn't shown for 3dmigoto fixes when key type was set to "toggle"[/.] [.]Bugfix: Updating all installed 3dmigoto wrappers was broken in "Application Settings" tab[/.] [/list]
Version 1.64 released

Change notes:

  • New: Supported resolutions and refresh rates of the primary display are automatically detected. To enable this feature go to "Display Profiles" tab and link your display to your desired display profile.

  • New: Supported resolutions are cached in a file for faster accessing this information

  • New: When updating all installed 3dmigoto wrappers the dialog window tells you how many games have been updated.

  • Changed: By default IR output mode isn't changed any more when applying settings in "Nvidia 3D Settings" tab or when skipping 3D Vision setup wizard. For changing IR mode you have to manually tick the option "Sync mode of IR Sender" in "Nvidia 3D Settings" tab first.

  • Changed: Search text for filtering games doesn't need to be so precise any more. So for example it doesn't matter if you type in "Assassin's Creed" or "assassinscreed" for listing all AC games.

  • Changed: Updated 3dmigoto files to version 1.3.12

  • Changed: Reworked some tooltips in "Hotkeys" tab

  • Bugfix: Synchronization between glasses and IR emitter could break when applying settings in "Nvidia 3D Settings" tab

  • Bugfix: "Delay" option in "Hotkeys" tab wasn't shown for 3dmigoto fixes when key type was either set to "cycle" or "toggle"

  • Bugfix: "Release Transition" option in "Hotkeys" tab wasn't shown for 3dmigoto fixes when key type was set to "toggle"

  • Bugfix: Updating all installed 3dmigoto wrappers was broken in "Application Settings" tab

ASUS ROG Strix GeForce GTX 1080 | Core I7-7700K | 16GB RAM | Win10 Pro x64
Asus ROG Swift PG278Q 3D Vision Monitor
Optoma UHD 40 3D Vision Projector
Paypal donations for 3D Fix Manager: duselpaul86@gmx.de

Posted 12/06/2018 02:09 PM   
[quote="TimFx7"]I forgot to mention an important point . I'm doing quick setup in every driver installation. ( Advanced 3D Vision Configuration 1.4 ) I'm loading the settings from an xml file. (skipping the 3D Vision setup wizard) I've been using this way for 3 years. Although 3D running smoothly, xml file "StereoIROutput and StereoFlywheelCycleState" do not have these values. I probably would not be a problem on 3DFM if I had used 3D Vision setup wizard.[/quote] Quick setup should be safe to use again in 3DFM. Please report if there are any further bugs ;D. Btw synchronization also works without the two Registry entries. So best thing is to ignore that IR setting unless you want to use Multi IR or LAN environment. But using this option should not produce any bugs / sync issues any more.
TimFx7 said:I forgot to mention an important point . I'm doing quick setup in every driver installation. ( Advanced 3D Vision Configuration 1.4 ) I'm loading the settings from an xml file. (skipping the 3D Vision setup wizard)
I've been using this way for 3 years. Although 3D running smoothly, xml file "StereoIROutput and StereoFlywheelCycleState" do not have these values. I probably would not be a problem on 3DFM if I had used 3D Vision setup wizard.


Quick setup should be safe to use again in 3DFM. Please report if there are any further bugs ;D. Btw synchronization also works without the two Registry entries. So best thing is to ignore that IR setting unless you want to use Multi IR or LAN environment. But using this option should not produce any bugs / sync issues any more.

ASUS ROG Strix GeForce GTX 1080 | Core I7-7700K | 16GB RAM | Win10 Pro x64
Asus ROG Swift PG278Q 3D Vision Monitor
Optoma UHD 40 3D Vision Projector
Paypal donations for 3D Fix Manager: duselpaul86@gmx.de

Posted 12/06/2018 02:19 PM   
[quote="rustyk21"]Good team work :-) @Pauldusler, it was Divinity Original Sin Enhanced edition that exhibited the behaivour of appearing to be uninstalled. I wouldn't worry about it until I manage to recreate the steps reliably, it's probably a better use of your time to concentrate on other things :-) [/quote] Btw I didn't have any launch / uninstall issues on Steam with this game. SteamDB says that this game has only 1 SteamApp ID. So my first assumption about different IDs was wrong. My next guess would be that your Steam installation is somehow wrong. There are a lot of people who reinstall Windows but not Steam. Therefore Windows doesn't know anything that Steam exists on the hard drive. Maybe the issue comes from there (again a wild guess :D) But I remember that I had the same issue when I used an older Windows 10 version. The issue happened when the computer crashed with a bluescreen when starting a game via Steam. Then next time I wanted to start the same game Steam started to reinstall it. I never experienced such bluescreens anymore on Windows 10 v. 1709 and higher.
rustyk21 said:Good team work :-)

@Pauldusler, it was Divinity Original Sin Enhanced edition that exhibited the behaivour of appearing to be uninstalled. I wouldn't worry about it until I manage to recreate the steps reliably, it's probably a better use of your time to concentrate on other things :-)


Btw I didn't have any launch / uninstall issues on Steam with this game. SteamDB says that this game has only 1 SteamApp ID. So my first assumption about different IDs was wrong. My next guess would be that your Steam installation is somehow wrong. There are a lot of people who reinstall Windows but not Steam. Therefore Windows doesn't know anything that Steam exists on the hard drive. Maybe the issue comes from there (again a wild guess :D)

But I remember that I had the same issue when I used an older Windows 10 version. The issue happened when the computer crashed with a bluescreen when starting a game via Steam. Then next time I wanted to start the same game Steam started to reinstall it. I never experienced such bluescreens anymore on Windows 10 v. 1709 and higher.

ASUS ROG Strix GeForce GTX 1080 | Core I7-7700K | 16GB RAM | Win10 Pro x64
Asus ROG Swift PG278Q 3D Vision Monitor
Optoma UHD 40 3D Vision Projector
Paypal donations for 3D Fix Manager: duselpaul86@gmx.de

Posted 12/06/2018 03:40 PM   
Btw another thing I just wanted to mention: lou4612 was the first one + another guy who reported the bug about broken sync of the glasses. This was in September 2018. He said that applying Nvidia 3D Settings would break 3D. I asked both of them to supply screenshots of the registry key before and after they clicked on the apply button in 3DFM. Their reaction was null. But 3 monthts later on 3rd December lou4612 reported back that this bug still exists. Sorry, I just want to say that things don't work like this. It's good that you report bugs but they cannot be solved if you just complain several times that they are still not fixed although you didn't supply further feedback. Just want to say that's not an efficient way if you want to have bugs fixed. You see what happened: TimFX uploaded screenshots instead of you and the bug was fixed in 2 days. If you had supplied a screenshot the bug would have been eliminated still in September. We have to work together if we want to solve bugs quickly...
Btw another thing I just wanted to mention:

lou4612 was the first one + another guy who reported the bug about broken sync of the glasses. This was in September 2018. He said that applying Nvidia 3D Settings would break 3D. I asked both of them to supply screenshots of the registry key before and after they clicked on the apply button in 3DFM. Their reaction was null. But 3 monthts later on 3rd December lou4612 reported back that this bug still exists.

Sorry, I just want to say that things don't work like this. It's good that you report bugs but they cannot be solved if you just complain several times that they are still not fixed although you didn't supply further feedback. Just want to say that's not an efficient way if you want to have bugs fixed. You see what happened: TimFX uploaded screenshots instead of you and the bug was fixed in 2 days. If you had supplied a screenshot the bug would have been eliminated still in September. We have to work together if we want to solve bugs quickly...

ASUS ROG Strix GeForce GTX 1080 | Core I7-7700K | 16GB RAM | Win10 Pro x64
Asus ROG Swift PG278Q 3D Vision Monitor
Optoma UHD 40 3D Vision Projector
Paypal donations for 3D Fix Manager: duselpaul86@gmx.de

Posted 12/06/2018 05:43 PM   
Hey, i've got a weird bug with my mouse inputs when using 3D Vision fix manager. When I launch a game through 3D Vision Fix manager, the game no longer receives the "back", "forward", and other custom mouse inputs. When I launch the game normally, the mouse works normally. My mouse is a Logitech Performance MX (wireless, uses Logitech's universal "Unifying" transmitter). The custom keys are set using Logitech's Setpoint software). The game I'm trying to play is Warframe (non-steam intallation : autonomous installation from the game's official website), I had to add custom profile because 3D Vision fix manager did not recognize the game was installed, [s]and I'm not sure everything is setup correctly.[/s] [s] By the way I've had a lot of difficulties with setting all the paths, and I'm not sure they're correct if in the future I'd want to try shaderfixing, because this game's launcher is located in the user's appdata folder, whereas the game's actual exe is located in a different directory (e:/)[/s] EDIT : I noticed that 3D Fix manager itself does not listen to the custom mouse inputs. I found this out because one of my mouse keys is set to redirect to a keyboard key, and 3D Fix Manager does not show this input when I try it. Has anyone else had this issue ? Any ideas of where the issue could be coming from ? [s](wrong setting in the profile ?)[/s]
Hey, i've got a weird bug with my mouse inputs when using 3D Vision fix manager.

When I launch a game through 3D Vision Fix manager, the game no longer receives the "back", "forward", and other custom mouse inputs.
When I launch the game normally, the mouse works normally.

My mouse is a Logitech Performance MX (wireless, uses Logitech's universal "Unifying" transmitter). The custom keys are set using Logitech's Setpoint software).
The game I'm trying to play is Warframe (non-steam intallation : autonomous installation from the game's official website), I had to add custom profile because 3D Vision fix manager did not recognize the game was installed, and I'm not sure everything is setup correctly.

By the way I've had a lot of difficulties with setting all the paths, and I'm not sure they're correct if in the future I'd want to try shaderfixing, because this game's launcher is located in the user's appdata folder, whereas the game's actual exe is located in a different directory (e:/)


EDIT : I noticed that 3D Fix manager itself does not listen to the custom mouse inputs.
I found this out because one of my mouse keys is set to redirect to a keyboard key, and 3D Fix Manager does not show this input when I try it.

Has anyone else had this issue ? Any ideas of where the issue could be coming from ? (wrong setting in the profile ?)

Passive 3D forever
110" DIY dual-projection system
2x Epson EH-TW3500 (1080p) + Linear Polarizers (SPAR)
XtremScreen Daylight 2.0
VNS Geobox501 signal converter

Posted 12/17/2018 02:26 PM   
Hi Blackshark! I'm also using custom keys for my mouse (Logitech G402). One mouse button is redirected to ESC and the other one to ENTER. And both work for hotkey editing and also while gaming. Your mouse seems to be a bit old (2009)? Also Set Point - if I remember correctly this was the mouse software one had used 10 years ago or so? Maybe just the mouse or the software is too old. But I know that Logitech is lazy and does not want to provide support for older devices in logitech gaming software. Maybe worth a try to test if the same issues exist with a newer mouse if you have one. Would be interesting to know! Cheers!
Hi Blackshark!

I'm also using custom keys for my mouse (Logitech G402). One mouse button is redirected to ESC and the other one to ENTER. And both work for hotkey editing and also while gaming. Your mouse seems to be a bit old (2009)? Also Set Point - if I remember correctly this was the mouse software one had used 10 years ago or so? Maybe just the mouse or the software is too old. But I know that Logitech is lazy and does not want to provide support for older devices in logitech gaming software.

Maybe worth a try to test if the same issues exist with a newer mouse if you have one. Would be interesting to know!

Cheers!

ASUS ROG Strix GeForce GTX 1080 | Core I7-7700K | 16GB RAM | Win10 Pro x64
Asus ROG Swift PG278Q 3D Vision Monitor
Optoma UHD 40 3D Vision Projector
Paypal donations for 3D Fix Manager: duselpaul86@gmx.de

Posted 12/17/2018 04:55 PM   
  53 / 60    
Scroll To Top