search

matthieupoyade / quadifier

Automatically exported from code.google.com/p/quadifier
0 stars 0 forks source link

Failed to inject DLL error + no stereo rendering #5

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Hi,

Thanks for sharing the source code of your project.
I have the following issue
What steps will reproduce the problem?

1. Desktop PC
   - Intel Core i7
   - Unity Free 4.6
   - NVIDIA Quadro Fx 3800 with 1GB GDDR3 dedicated memory
   - Windows 7x64 Professional
   - Enabled stereo 3D on NVidia Control Panel
   - Projector refresh rate is 120 Hz
   - 1 screen
2. I built the project with Visual Studio 2010 and DirectX 11 SDK into Release 
applications (I got launcher.exe and module DLL in the Release folder without 
any errors). I edited the settings file to put my screen specs
3. I built the CAVEUnity1 project into a Standalone application with Direct3D
I dragged it into launcher.exe, then got an error on the console "failed to 
inject" twice...The application runs, but stereo is not activated

Q2: What is the expected output? What do you see instead?
What is the expected output? What do you see instead?
I was expecting active stereo rendering, I get the 3D scene but no stereo 
rendering
What version of the product are you using? On what operating system?
Quadifier, Unity 4.6 Free on Windows 7 64 pro

Please provide any additional information below.

Thanks a lot,

Amine

Original issue reported on code.google.com by amine.ch...@gmail.com on 3 Apr 2015 at 4:42

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Hi,
I have the same problem, with the following environment:
- windows 7, 64
- visual studio 2013
- 2x Nvidia Quadro 6000
(and a 4 wall cube to play with :) )

Then compiling in 32bits mode, I get exactly the same pb (injection does not 
work). Then compiling in 64bits mode, the Unity.exe file crashes. I guess that 
the injection works (difficult to check) and crashes the application. I will 
try another DLLinjector to check if the problem comes from the launcher or from 
the injected DLL. 

Any help appreciated :) :) 

P.S.: I will post again after I find a solution

Original comment by JeanLuc....@gmail.com on 19 Jun 2015 at 2:06