I wonder when there will be a fix for Space Engineers.
So love the game.
Unfortunatly, 3D gaming and developpers not go hand in hand.
Ok, i tried to fix the shaders myself with the HelixMod (DEBUGGER) but i see that the character in 3rd person view is totally to the left of the screen and as the fix only disables shaders i understand there is no fix made. This is easy to fix by developpers as they know there are people that play in 3D.
Developper simply stated: Disable 3dVision in the control panel.... well if that's all the developpers can say about that i don't buy the oculus rift aswell just because of this. They must work together or make each shader seperate and all the troubles that can cause with 3D they must already fixed in their games. There is not an Oculus Rift DK (Development Kit) on the market just for gamers...... Anyway..... I know that this won't help anything but it must been said......
That's why i don't buy games anymore and also no 3D stuff anymore...
Shame of the money i put in the 3D monitor and the 3D-Vision 2 Kit.
Also it crashes the game everytime on 32bit. My computer is 64bit
It has a Bin64 folder and just a Bin folder which is 32bit version of the game, and i assume the d3d9.dll (debug) is 32bit only??? so i put the dll in the Bin folder where the .exe also is along with the DX9Settings.ini
Started the game and see red debug letters so i scrolled through the shaders. Hitted numpad 6 or 3 to save the shader. Edit it notepad++ and put that 8 digit for example: 66FBFFF8.txt in the ...\Space Engineers Bin\ShaderOverride\VertexShaders folder.
So my Bin directory looks like this:
--------------------------------
Dumps (folder)
[.]PixelShaders (folder)[/.]
[.]VertexShaders (folder)[/.]
Profile (folder)
ShaderOverride (folder)
[.]PixelShaders (folder)[/.]
[.]VertexShaders (folder)[/.]
DX9Settings.ini
SpaceEngineers.ico
SpaceEngineers.exe
d3d9.dll (DEBUG VERSION)
D3DX9_43.dll (this is also a game file but maybe this causes the crash???)
...
and the rest of the game files
So i wonder if this crash causes by the shaderhack, cause thats what it is basicaly, or is it just the game because i run it 32bit?
LOG.txt file of the game gave me this error multiple times:
GetDirect3D
Deleting hash: 0 pointer 2E86BCE0 pool 2
It even crash without the fixed file in the VertexShader folder. So i think its the game, i try 64 bit though.... i saw the 64bit version of the d3d9.dll... That was my fault.... i try again :)
Okay, i tried with newer version of the game, 01.108 with planets, and it crashes with the d3d9.dll (64bit) Debugger as soon as i start the game. The menu won't even load up.
Same LOG.txt error though
GetDirect3D
Deleting hash: 0 pointer 3499DE50 pool 2
So unfortunatly now i know why this has no 3D fix.
I wonder when there will be a fix for Space Engineers.
So love the game.
Unfortunatly, 3D gaming and developpers not go hand in hand.
Ok, i tried to fix the shaders myself with the HelixMod (DEBUGGER) but i see that the character in 3rd person view is totally to the left of the screen and as the fix only disables shaders i understand there is no fix made. This is easy to fix by developpers as they know there are people that play in 3D.
Developper simply stated: Disable 3dVision in the control panel.... well if that's all the developpers can say about that i don't buy the oculus rift aswell just because of this. They must work together or make each shader seperate and all the troubles that can cause with 3D they must already fixed in their games. There is not an Oculus Rift DK (Development Kit) on the market just for gamers...... Anyway..... I know that this won't help anything but it must been said......
That's why i don't buy games anymore and also no 3D stuff anymore...
Shame of the money i put in the 3D monitor and the 3D-Vision 2 Kit.
Also it crashes the game everytime on 32bit. My computer is 64bit
It has a Bin64 folder and just a Bin folder which is 32bit version of the game, and i assume the d3d9.dll (debug) is 32bit only??? so i put the dll in the Bin folder where the .exe also is along with the DX9Settings.ini
Started the game and see red debug letters so i scrolled through the shaders. Hitted numpad 6 or 3 to save the shader. Edit it notepad++ and put that 8 digit for example: 66FBFFF8.txt in the ...\Space Engineers Bin\ShaderOverride\VertexShaders folder.
So my Bin directory looks like this:
--------------------------------
Dumps (folder)
PixelShaders (folder)
VertexShaders (folder)
Profile (folder)
ShaderOverride (folder)
PixelShaders (folder)
VertexShaders (folder)
DX9Settings.ini
SpaceEngineers.ico
SpaceEngineers.exe
d3d9.dll (DEBUG VERSION)
D3DX9_43.dll (this is also a game file but maybe this causes the crash???)
...
and the rest of the game files
So i wonder if this crash causes by the shaderhack, cause thats what it is basicaly, or is it just the game because i run it 32bit?
LOG.txt file of the game gave me this error multiple times:
GetDirect3D
Deleting hash: 0 pointer 2E86BCE0 pool 2
It even crash without the fixed file in the VertexShader folder. So i think its the game, i try 64 bit though.... i saw the 64bit version of the d3d9.dll... That was my fault.... i try again :)
Okay, i tried with newer version of the game, 01.108 with planets, and it crashes with the d3d9.dll (64bit) Debugger as soon as i start the game. The menu won't even load up.
Same LOG.txt error though
GetDirect3D
Deleting hash: 0 pointer 3499DE50 pool 2
So unfortunatly now i know why this has no 3D fix.
The Steam overlay sometimes causes crashes with helixmod. Try going into your Steam folder and deleting GameOverlayRenderer.dll and GameOverlayRenderer64.dll - they'll come back every time Steam is restarted though.
The Steam overlay sometimes causes crashes with helixmod. Try going into your Steam folder and deleting GameOverlayRenderer.dll and GameOverlayRenderer64.dll - they'll come back every time Steam is restarted though.
[quote="Pirateguybrush"]The Steam overlay sometimes causes crashes with helixmod. Try going into your Steam folder and deleting GameOverlayRenderer.dll and GameOverlayRenderer64.dll - they'll come back every time Steam is restarted though.[/quote]
Can i just disable the overlay in steam settings or is that some kind different?
Well, i disabled it in settings in steam and also deleted the GameOverlayRenderer.dll and GameOverlayRenderer64.dll from the steam folder and now it starts the game which facing me into another problem.
The worlds with planets are DX11 while the older worlds are DX9 so i try to do the DX9 first.
Thanks for your tip :)
EDIT:
Well, the tip not lasted for long, after a while it still crashes when i scroll through the shaders or if i moved my mouse. Seems that the game has some issues cause i tried the fix with The Ball game and that worked.....
Pirateguybrush said:The Steam overlay sometimes causes crashes with helixmod. Try going into your Steam folder and deleting GameOverlayRenderer.dll and GameOverlayRenderer64.dll - they'll come back every time Steam is restarted though.
Can i just disable the overlay in steam settings or is that some kind different?
Well, i disabled it in settings in steam and also deleted the GameOverlayRenderer.dll and GameOverlayRenderer64.dll from the steam folder and now it starts the game which facing me into another problem.
The worlds with planets are DX11 while the older worlds are DX9 so i try to do the DX9 first.
Thanks for your tip :)
EDIT:
Well, the tip not lasted for long, after a while it still crashes when i scroll through the shaders or if i moved my mouse. Seems that the game has some issues cause i tried the fix with The Ball game and that worked.....
Disabling the overlay in the settings doesn't prevent the problem, you have to delete the files. Glad that helped.
That's very strange, having the game part DX9 and part DX11. Does it launch the old and new world from the same exe file, or are there two versions?
Does the crashing happen on both DX9 and DX11?
[quote="Pirateguybrush"]Disabling the overlay in the settings doesn't prevent the problem, you have to delete the files. Glad that helped.
That's very strange, having the game part DX9 and part DX11. Does it launch the old and new world from the same exe file, or are there two versions?
Does the crashing happen on both DX9 and DX11?[/quote]
Well, as the fix is d3d9.dll it's for dx9 so that's why i do the dx9 but still keep crashing.
Also i re-assigned the hotkeys in the DX9Settings.ini and also with that it crashes sometimes.
The keys work though but it crashes. So i think i give up on this one. Game is just Unity game and its buggy as hell like most Unity games are.
LOG.txt is now:
GetDirect3D
Deleting hash: 0 pointer 45FE21E0 pool 2
pD3DXAssembleShaderFromFile
Seeing this last log file tells me something about D3DX9_43.dll that came with the game that also resides in the Bin64 folder of the game.
pD3DXAssembleShaderFromFile seems to point to the D3DX9_43.dll as the D3DX in the name says.....
So i guess there is an issue with two .dll files in that Bin64 folder that already does something with DX9
Pirateguybrush said:Disabling the overlay in the settings doesn't prevent the problem, you have to delete the files. Glad that helped.
That's very strange, having the game part DX9 and part DX11. Does it launch the old and new world from the same exe file, or are there two versions?
Does the crashing happen on both DX9 and DX11?
Well, as the fix is d3d9.dll it's for dx9 so that's why i do the dx9 but still keep crashing.
Also i re-assigned the hotkeys in the DX9Settings.ini and also with that it crashes sometimes.
The keys work though but it crashes. So i think i give up on this one. Game is just Unity game and its buggy as hell like most Unity games are.
LOG.txt is now:
GetDirect3D
Deleting hash: 0 pointer 45FE21E0 pool 2
pD3DXAssembleShaderFromFile
Seeing this last log file tells me something about D3DX9_43.dll that came with the game that also resides in the Bin64 folder of the game.
pD3DXAssembleShaderFromFile seems to point to the D3DX9_43.dll as the D3DX in the name says.....
So i guess there is an issue with two .dll files in that Bin64 folder that already does something with DX9
[quote="ProgNoizes"][quote="Pirateguybrush"]
That's very strange, having the game part DX9 and part DX11. Does it launch the old and new world from the same exe file, or are there two versions?
[/quote]
First of all, it's one file called Space Engineers.exe, and in the menu when the game is started you can choose worlds, also worlds with planets, when select world with a planet, game asks to switch to DX11 in the menu of the game. If select world without planets, so the older ones before 0.1.108 version of the game, it uses DX9.
The DX11 version of the game won't even go in 3D mode, the emitter is ON but there is no double screen so that's a no go.
Better not buy 3D glasses peeps.... This is the result..
Pirateguybrush said:
That's very strange, having the game part DX9 and part DX11. Does it launch the old and new world from the same exe file, or are there two versions?
First of all, it's one file called Space Engineers.exe, and in the menu when the game is started you can choose worlds, also worlds with planets, when select world with a planet, game asks to switch to DX11 in the menu of the game. If select world without planets, so the older ones before 0.1.108 version of the game, it uses DX9.
The DX11 version of the game won't even go in 3D mode, the emitter is ON but there is no double screen so that's a no go.
Better not buy 3D glasses peeps.... This is the result..
Actually this isn't running Unity, it's running on an engine called VRAGE 2.0
http://www.keenswh.com/vrage.html
I can hazard a guess at what might be going on though. Some Unity games are unstable under helixmod, specifically when the camera is moved. It's possible this is the case under VRAGE as well. If you don't touch the mouse/camera while hunting shaders, will it still crash?
As for DX11, it's likely running in borderless window mode. 3D won't kick in for this mode. Can you look for a way to set it to true fullscreen?
I can hazard a guess at what might be going on though. Some Unity games are unstable under helixmod, specifically when the camera is moved. It's possible this is the case under VRAGE as well. If you don't touch the mouse/camera while hunting shaders, will it still crash?
As for DX11, it's likely running in borderless window mode. 3D won't kick in for this mode. Can you look for a way to set it to true fullscreen?
[quote="Pirateguybrush"]Actually this isn't running Unity, it's running on an engine called VRAGE 2.0
http://www.keenswh.com/vrage.html
I can hazard a guess at what might be going on though. Some Unity games are unstable under helixmod, specifically when the camera is moved. It's possible this is the case under VRAGE as well. If you don't touch the mouse/camera while hunting shaders, will it still crash?
As for DX11, it's likely running in borderless window mode. 3D won't kick in for this mode. Can you look for a way to set it to true fullscreen?[/quote]
Sometimes it crashes when i hunt shaders, it crashed 1 time when i wanted to load the new fixed shader in i guess PixelShader folder but i was thinking, isn't that for when the game starts? and VertexShaders i can reload while the game is running?? i guess so... and maybe it crashes because i do alt-TAB and back to the game again, then hunt shaders?? must be no problem but hey, not every game/engine is the same...
I run some more tests... in DX 11 i try to set it on full modus as that can be indeed the thing i remember now you say that.....
ABOUT THE BORDERLESS WINDOW MODE:
Ok, i looked for the resolution and it's set on 1920x1080 and Full Windowed. There are 3 options in the game menu:
FULLSCREEN WINDOW
FULLSCREEN
WINDOW
There is a file in AppData\Roaming\SpaceEngineers folder called SpaceEngineers.cfg that states
<item>
<Key xsi:type="xsd:string">ScreenWidth</Key>
<Value xsi:type="xsd:string">1920</Value>
</item>
<item>
<Key xsi:type="xsd:string">ScreenHeight</Key>
<Value xsi:type="xsd:string">1080</Value>
</item>
<item>
<item>
<Key xsi:type="xsd:string">WindowMode</Key>
<Value xsi:type="xsd:string">2</Value>
</item>
2 is FULLSCREEN
1 is FULLSCREEN WINDOW (Windowed Borderless how we call it)
0 is WINDOW
So it was already set to true full screen
I tested it by setting the 2 to 1 and started the game and looked what the option was set on and was on FULL WINDOWED. Then in game i set it to FULL SCREEN, then exit the game and opened the file and was back to 2. So i figured out wat each number is.
As for testing the shader hunt, that doesn't crash
I tested the shader hunt for 10 minutes straight without touching anything else.
I tested the keys i assigned like numpad 1, 2, 3, 4, 5, 6 etc, those works good.
BUT, as soon as i move the mouse and again try to hunt shaders, it crashes instantly without logging it.
LOG.txt does not says anything this time.
This is all with DX9 as DX11 won't even turn on 3D
EDIT*
After some more testing it crashed when only shader hunting
I didn't touched the mouse or anything else then the test before this test.
So YES it crashes also when only hunt shaders.
But this time i got a log:
GetDirect3D
Deleting hash: 0 pointer 4F22D610 pool 2
D3DUSAGE_RENDERTARGET/D3DUSAGE_DEPTHSTENCIL Height 672 Width 1200 Usage 1 Format 21 Pool 0 Levels 0 texptr 0 nIndex 0, Mode 0
I can hazard a guess at what might be going on though. Some Unity games are unstable under helixmod, specifically when the camera is moved. It's possible this is the case under VRAGE as well. If you don't touch the mouse/camera while hunting shaders, will it still crash?
As for DX11, it's likely running in borderless window mode. 3D won't kick in for this mode. Can you look for a way to set it to true fullscreen?
Sometimes it crashes when i hunt shaders, it crashed 1 time when i wanted to load the new fixed shader in i guess PixelShader folder but i was thinking, isn't that for when the game starts? and VertexShaders i can reload while the game is running?? i guess so... and maybe it crashes because i do alt-TAB and back to the game again, then hunt shaders?? must be no problem but hey, not every game/engine is the same...
I run some more tests... in DX 11 i try to set it on full modus as that can be indeed the thing i remember now you say that.....
ABOUT THE BORDERLESS WINDOW MODE:
Ok, i looked for the resolution and it's set on 1920x1080 and Full Windowed. There are 3 options in the game menu:
FULLSCREEN WINDOW
FULLSCREEN
WINDOW
There is a file in AppData\Roaming\SpaceEngineers folder called SpaceEngineers.cfg that states
2 is FULLSCREEN
1 is FULLSCREEN WINDOW (Windowed Borderless how we call it)
0 is WINDOW
So it was already set to true full screen
I tested it by setting the 2 to 1 and started the game and looked what the option was set on and was on FULL WINDOWED. Then in game i set it to FULL SCREEN, then exit the game and opened the file and was back to 2. So i figured out wat each number is.
As for testing the shader hunt, that doesn't crash
I tested the shader hunt for 10 minutes straight without touching anything else.
I tested the keys i assigned like numpad 1, 2, 3, 4, 5, 6 etc, those works good.
BUT, as soon as i move the mouse and again try to hunt shaders, it crashes instantly without logging it.
LOG.txt does not says anything this time.
This is all with DX9 as DX11 won't even turn on 3D
EDIT*
After some more testing it crashed when only shader hunting
I didn't touched the mouse or anything else then the test before this test.
So YES it crashes also when only hunt shaders.
But this time i got a log:
GetDirect3D
Deleting hash: 0 pointer 4F22D610 pool 2
D3DUSAGE_RENDERTARGET/D3DUSAGE_DEPTHSTENCIL Height 672 Width 1200 Usage 1 Format 21 Pool 0 Levels 0 texptr 0 nIndex 0, Mode 0
Since dx9 games require using the helixmod, you have to try each version to get a working wrapper (the latest version has more features but will not necessarily be the one that works). helix, no longer releases new versions, so it's possible that none of his wrappers will work properly with this Engine. These wrappers are often incompatible with overlays like MSI Afterburner or Steam's, as pointed out by pirateguybrush.
Since this game is "early access", if you are able to fix things, you'll likely have to redo everything anytime a patch is released.
So you might want to try using compatibility mode in dx11 while the game is in development. There's a sticky for doing so, here on the forum.
For Fullscreen, it's possible that chiri's resolution tool can force it. It pretty hit or miss and only seems to work with a few games.
http://helixmod.blogspot.com/2013/02/chiris-force-certain-resolutionhertz.html
You can try convincing the developer to add the option for fullscreen.
If you were to go the dx11 route, 3Dmigoto has a force fullscreen option.
Too bad that it's not using Unity dx9, Darkstarsword has some tricks for fixing things on his site.
(dx11 too I think)
[quote="DarkStarSword"]If you wanted to take a crack at fixing it yourself, I have templates that can often fix Unity lights/shadows in my 3d-fixes repository, and my shadertool.py script can fix most of the other serious problems (but if you switched profile the driver may be doing that part already - if you get flickering return to the original profile and use my script instead).[/quote]
Disclaimer: I'm not a shaderhacker, these are things I've picked up from reading the forums
Since dx9 games require using the helixmod, you have to try each version to get a working wrapper (the latest version has more features but will not necessarily be the one that works). helix, no longer releases new versions, so it's possible that none of his wrappers will work properly with this Engine. These wrappers are often incompatible with overlays like MSI Afterburner or Steam's, as pointed out by pirateguybrush.
Since this game is "early access", if you are able to fix things, you'll likely have to redo everything anytime a patch is released.
So you might want to try using compatibility mode in dx11 while the game is in development. There's a sticky for doing so, here on the forum.
You can try convincing the developer to add the option for fullscreen.
If you were to go the dx11 route, 3Dmigoto has a force fullscreen option.
Too bad that it's not using Unity dx9, Darkstarsword has some tricks for fixing things on his site.
(dx11 too I think)
DarkStarSword said:If you wanted to take a crack at fixing it yourself, I have templates that can often fix Unity lights/shadows in my 3d-fixes repository, and my shadertool.py script can fix most of the other serious problems (but if you switched profile the driver may be doing that part already - if you get flickering return to the original profile and use my script instead).
Disclaimer: I'm not a shaderhacker, these are things I've picked up from reading the forums
Well, i tried 3DMigoto x64 version 1.2.7 and 1.2.6 and 1.2.1 now but so far, same results
The game starts in DX11 because i chosen that before installing 3DMigoto, also the resolution was already 1920x1080 and FULLSCREEN was selected so i installed the files in the Bin64 folder and started the game as admin. Took a while to load which explaned so that's okay. I could hunt shaders without problem, kinda laggy though but no problem, but there was no 3D, even when i tried to switch to Compatibility Mode.
I installed 3DMigoto on a clean unmodded game like explaned
I played around with
https://forums.geforce.com/default/topic/791450/?comment=4374239
to make it in Compatibility Mode but it did not say it was in Compatibility Mode, even not with CTRL-F11
Also i pasted this line in the NVIDIA Profiles.txt and re-imported it after delleting the nvdrssel.bin for the second time, because i had to export it and delete it as explaned on the site.
Setting ID_0x709adada = 0x07f58257 InternalSettingFlag=V0
So i guess the other versions of 3DMigoto also not work. I tried 3 versions..... all 3 exact same results
The http://helixmod.blogspot.com/2013/02/chiris-force-certain-resolutionhertz.html i tried in the 32bit version cause it was explaned that this only works for 32bit games but the game crashes at startup. GameOverlayRenderer.dll and GameOverlayRenderer64.dll are deleted from steam folder so that was not the problem. I did tried to change resolution and hertz in the d3dx.ini file but it crashed aswell. :(
Also i tried 3DMigoto 1.1.36 but offcourse, did not work.
It start to feel hopeless :(
Well, i tried 3DMigoto x64 version 1.2.7 and 1.2.6 and 1.2.1 now but so far, same results
The game starts in DX11 because i chosen that before installing 3DMigoto, also the resolution was already 1920x1080 and FULLSCREEN was selected so i installed the files in the Bin64 folder and started the game as admin. Took a while to load which explaned so that's okay. I could hunt shaders without problem, kinda laggy though but no problem, but there was no 3D, even when i tried to switch to Compatibility Mode.
I installed 3DMigoto on a clean unmodded game like explaned
I played around with
https://forums.geforce.com/default/topic/791450/?comment=4374239
to make it in Compatibility Mode but it did not say it was in Compatibility Mode, even not with CTRL-F11
Also i pasted this line in the NVIDIA Profiles.txt and re-imported it after delleting the nvdrssel.bin for the second time, because i had to export it and delete it as explaned on the site.
Setting ID_0x709adada = 0x07f58257 InternalSettingFlag=V0
So i guess the other versions of 3DMigoto also not work. I tried 3 versions..... all 3 exact same results
The http://helixmod.blogspot.com/2013/02/chiris-force-certain-resolutionhertz.html i tried in the 32bit version cause it was explaned that this only works for 32bit games but the game crashes at startup. GameOverlayRenderer.dll and GameOverlayRenderer64.dll are deleted from steam folder so that was not the problem. I did tried to change resolution and hertz in the d3dx.ini file but it crashed aswell. :(
Also i tried 3DMigoto 1.1.36 but offcourse, did not work.
Don't buy any 3D stuff people.. It's a rip off. VR is just a joke.
Even the glasses i can not sell because people don't trust it.
That's also the reason game developpers don't care.
Well, i don't care also anymore. I never buy a game anymore. i use google to get a game. Yes, for free.
This is what they all deserve. thanks for the free 2D shitty games....
Very mad at people. I don't care what i say anymore, i paid for this piece of sh¡t anywayzzz.
more then 600 bucks, and for what... 2D at 144 hertz.... What a fukking joke.
3d doesn't work, so i am left with 2D games at 144 hertz...
What the hell i need a 3D monitor for. Well foek all game developpers with their selling their game with VR/3Dvision compatibility sh¡t while it's not working.
Delete this post if you want, i don't care. I tell the truth and maybe people have to listen to complainers that paid big time money for something that just don't work.
Sh¡thole world!!!!!
Don't buy any 3D stuff people.. It's a rip off. VR is just a joke.
Even the glasses i can not sell because people don't trust it.
That's also the reason game developpers don't care.
Well, i don't care also anymore. I never buy a game anymore. i use google to get a game. Yes, for free.
This is what they all deserve. thanks for the free 2D shitty games....
Very mad at people. I don't care what i say anymore, i paid for this piece of sh¡t anywayzzz.
more then 600 bucks, and for what... 2D at 144 hertz.... What a fukking joke.
3d doesn't work, so i am left with 2D games at 144 hertz...
What the hell i need a 3D monitor for. Well foek all game developpers with their selling their game with VR/3Dvision compatibility sh¡t while it's not working.
Delete this post if you want, i don't care. I tell the truth and maybe people have to listen to complainers that paid big time money for something that just don't work.
Sh¡thole world!!!!!
[quote="ProgNoizes"]Don't buy any 3D stuff people.. It's a rip off. VR is just a joke.
Even the glasses i can not sell because people don't trust it.
That's also the reason game developpers don't care.
Well, i don't care also anymore. I never buy a game anymore. i use google to get a game. Yes, for free.
This is what they all deserve. thanks for the free 2D shitty games....
Very mad at people. I don't care what i say anymore, i paid for this piece of sh¡t anywayzzz.
more then 600 bucks, and for what... 2D at 144 hertz.... What a fukking joke.
3d doesn't work, so i am left with 2D games at 144 hertz...
What the hell i need a 3D monitor for. Well foek all game developpers with their selling their game with VR/3Dvision compatibility sh¡t while it's not working.
Delete this post if you want, i don't care. I tell the truth and maybe people have to listen to complainers that paid big time money for something that just don't work.
Sh¡thole world!!!!![/quote]
There are many games that work well in 3D, no need to throw a tantrum.
ProgNoizes said:Don't buy any 3D stuff people.. It's a rip off. VR is just a joke.
Even the glasses i can not sell because people don't trust it.
That's also the reason game developpers don't care.
Well, i don't care also anymore. I never buy a game anymore. i use google to get a game. Yes, for free.
This is what they all deserve. thanks for the free 2D shitty games....
Very mad at people. I don't care what i say anymore, i paid for this piece of sh¡t anywayzzz.
more then 600 bucks, and for what... 2D at 144 hertz.... What a fukking joke.
3d doesn't work, so i am left with 2D games at 144 hertz...
What the hell i need a 3D monitor for. Well foek all game developpers with their selling their game with VR/3Dvision compatibility sh¡t while it's not working.
Delete this post if you want, i don't care. I tell the truth and maybe people have to listen to complainers that paid big time money for something that just don't work.
Sh¡thole world!!!!!
There are many games that work well in 3D, no need to throw a tantrum.
[quote="ProgNoizes"]Very mad at people.[/quote]Well everyone here in the 3D Vision sub-forum is another disappointed, to one degree or another, 3D Vision user like yourself... there's rarely ever moderators in here, never mind anyone that actually really has anything to do with 3D Vision. We're all just users helping or at least trying to help other users.
As far as fixing a game goes... I'd suggest not jumping right into the unknown and start off slow, look into bo3b's lessons and after that possibly study an already fixed game and/or try to fix an already fixed game.
[url]https://forums.geforce.com/default/topic/766890/3d-vision/bo3bs-school-for-shaderhackers/[/url]
As far games in 3D game compatibility goes... there's plenty of older titles that run perfectly fine in 3D that are definitely worth replaying. On top of that there's tons of games that were fixed by the community on the HelixMod blog.
[url]http://helixmod.blogspot.com/2013/10/game-list-automatically-updated.html[/url]
Well everyone here in the 3D Vision sub-forum is another disappointed, to one degree or another, 3D Vision user like yourself... there's rarely ever moderators in here, never mind anyone that actually really has anything to do with 3D Vision. We're all just users helping or at least trying to help other users.
As far games in 3D game compatibility goes... there's plenty of older titles that run perfectly fine in 3D that are definitely worth replaying. On top of that there's tons of games that were fixed by the community on the HelixMod blog. http://helixmod.blogspot.com/2013/10/game-list-automatically-updated.html
So love the game.
Unfortunatly, 3D gaming and developpers not go hand in hand.
Ok, i tried to fix the shaders myself with the HelixMod (DEBUGGER) but i see that the character in 3rd person view is totally to the left of the screen and as the fix only disables shaders i understand there is no fix made. This is easy to fix by developpers as they know there are people that play in 3D.
Developper simply stated: Disable 3dVision in the control panel.... well if that's all the developpers can say about that i don't buy the oculus rift aswell just because of this. They must work together or make each shader seperate and all the troubles that can cause with 3D they must already fixed in their games. There is not an Oculus Rift DK (Development Kit) on the market just for gamers...... Anyway..... I know that this won't help anything but it must been said......
That's why i don't buy games anymore and also no 3D stuff anymore...
Shame of the money i put in the 3D monitor and the 3D-Vision 2 Kit.
Also it crashes the game everytime on 32bit. My computer is 64bit
It has a Bin64 folder and just a Bin folder which is 32bit version of the game, and i assume the d3d9.dll (debug) is 32bit only??? so i put the dll in the Bin folder where the .exe also is along with the DX9Settings.ini
Started the game and see red debug letters so i scrolled through the shaders. Hitted numpad 6 or 3 to save the shader. Edit it notepad++ and put that 8 digit for example: 66FBFFF8.txt in the ...\Space Engineers Bin\ShaderOverride\VertexShaders folder.
So my Bin directory looks like this:
--------------------------------
Dumps (folder)
ShaderOverride (folder)
SpaceEngineers.ico
SpaceEngineers.exe
d3d9.dll (DEBUG VERSION)
D3DX9_43.dll (this is also a game file but maybe this causes the crash???)
...
and the rest of the game files
So i wonder if this crash causes by the shaderhack, cause thats what it is basicaly, or is it just the game because i run it 32bit?
LOG.txt file of the game gave me this error multiple times:
GetDirect3D
Deleting hash: 0 pointer 2E86BCE0 pool 2
It even crash without the fixed file in the VertexShader folder. So i think its the game, i try 64 bit though.... i saw the 64bit version of the d3d9.dll... That was my fault.... i try again :)
Okay, i tried with newer version of the game, 01.108 with planets, and it crashes with the d3d9.dll (64bit) Debugger as soon as i start the game. The menu won't even load up.
Same LOG.txt error though
GetDirect3D
Deleting hash: 0 pointer 3499DE50 pool 2
So unfortunatly now i know why this has no 3D fix.
Can i just disable the overlay in steam settings or is that some kind different?
Well, i disabled it in settings in steam and also deleted the GameOverlayRenderer.dll and GameOverlayRenderer64.dll from the steam folder and now it starts the game which facing me into another problem.
The worlds with planets are DX11 while the older worlds are DX9 so i try to do the DX9 first.
Thanks for your tip :)
EDIT:
Well, the tip not lasted for long, after a while it still crashes when i scroll through the shaders or if i moved my mouse. Seems that the game has some issues cause i tried the fix with The Ball game and that worked.....
That's very strange, having the game part DX9 and part DX11. Does it launch the old and new world from the same exe file, or are there two versions?
Does the crashing happen on both DX9 and DX11?
Well, as the fix is d3d9.dll it's for dx9 so that's why i do the dx9 but still keep crashing.
Also i re-assigned the hotkeys in the DX9Settings.ini and also with that it crashes sometimes.
The keys work though but it crashes. So i think i give up on this one. Game is just Unity game and its buggy as hell like most Unity games are.
LOG.txt is now:
GetDirect3D
Deleting hash: 0 pointer 45FE21E0 pool 2
pD3DXAssembleShaderFromFile
Seeing this last log file tells me something about D3DX9_43.dll that came with the game that also resides in the Bin64 folder of the game.
pD3DXAssembleShaderFromFile seems to point to the D3DX9_43.dll as the D3DX in the name says.....
So i guess there is an issue with two .dll files in that Bin64 folder that already does something with DX9
http://www.keenswh.com/vrage.html
I can hazard a guess at what might be going on though. Some Unity games are unstable under helixmod, specifically when the camera is moved. It's possible this is the case under VRAGE as well. If you don't touch the mouse/camera while hunting shaders, will it still crash?
As for DX11, it's likely running in borderless window mode. 3D won't kick in for this mode. Can you look for a way to set it to true fullscreen?
Sometimes it crashes when i hunt shaders, it crashed 1 time when i wanted to load the new fixed shader in i guess PixelShader folder but i was thinking, isn't that for when the game starts? and VertexShaders i can reload while the game is running?? i guess so... and maybe it crashes because i do alt-TAB and back to the game again, then hunt shaders?? must be no problem but hey, not every game/engine is the same...
I run some more tests... in DX 11 i try to set it on full modus as that can be indeed the thing i remember now you say that.....
ABOUT THE BORDERLESS WINDOW MODE:
Ok, i looked for the resolution and it's set on 1920x1080 and Full Windowed. There are 3 options in the game menu:
FULLSCREEN WINDOW
FULLSCREEN
WINDOW
There is a file in AppData\Roaming\SpaceEngineers folder called SpaceEngineers.cfg that states
<item>
<Key xsi:type="xsd:string">ScreenWidth</Key>
<Value xsi:type="xsd:string">1920</Value>
</item>
<item>
<Key xsi:type="xsd:string">ScreenHeight</Key>
<Value xsi:type="xsd:string">1080</Value>
</item>
<item>
<item>
<Key xsi:type="xsd:string">WindowMode</Key>
<Value xsi:type="xsd:string">2</Value>
</item>
2 is FULLSCREEN
1 is FULLSCREEN WINDOW (Windowed Borderless how we call it)
0 is WINDOW
So it was already set to true full screen
I tested it by setting the 2 to 1 and started the game and looked what the option was set on and was on FULL WINDOWED. Then in game i set it to FULL SCREEN, then exit the game and opened the file and was back to 2. So i figured out wat each number is.
As for testing the shader hunt, that doesn't crash
I tested the shader hunt for 10 minutes straight without touching anything else.
I tested the keys i assigned like numpad 1, 2, 3, 4, 5, 6 etc, those works good.
BUT, as soon as i move the mouse and again try to hunt shaders, it crashes instantly without logging it.
LOG.txt does not says anything this time.
This is all with DX9 as DX11 won't even turn on 3D
EDIT*
After some more testing it crashed when only shader hunting
I didn't touched the mouse or anything else then the test before this test.
So YES it crashes also when only hunt shaders.
But this time i got a log:
GetDirect3D
Deleting hash: 0 pointer 4F22D610 pool 2
D3DUSAGE_RENDERTARGET/D3DUSAGE_DEPTHSTENCIL Height 672 Width 1200 Usage 1 Format 21 Pool 0 Levels 0 texptr 0 nIndex 0, Mode 0
Since this game is "early access", if you are able to fix things, you'll likely have to redo everything anytime a patch is released.
So you might want to try using compatibility mode in dx11 while the game is in development. There's a sticky for doing so, here on the forum.
For Fullscreen, it's possible that chiri's resolution tool can force it. It pretty hit or miss and only seems to work with a few games.
http://helixmod.blogspot.com/2013/02/chiris-force-certain-resolutionhertz.html
You can try convincing the developer to add the option for fullscreen.
If you were to go the dx11 route, 3Dmigoto has a force fullscreen option.
Too bad that it's not using Unity dx9, Darkstarsword has some tricks for fixing things on his site.
(dx11 too I think)
Disclaimer: I'm not a shaderhacker, these are things I've picked up from reading the forums
The game starts in DX11 because i chosen that before installing 3DMigoto, also the resolution was already 1920x1080 and FULLSCREEN was selected so i installed the files in the Bin64 folder and started the game as admin. Took a while to load which explaned so that's okay. I could hunt shaders without problem, kinda laggy though but no problem, but there was no 3D, even when i tried to switch to Compatibility Mode.
I installed 3DMigoto on a clean unmodded game like explaned
I played around with
https://forums.geforce.com/default/topic/791450/?comment=4374239
to make it in Compatibility Mode but it did not say it was in Compatibility Mode, even not with CTRL-F11
Also i pasted this line in the NVIDIA Profiles.txt and re-imported it after delleting the nvdrssel.bin for the second time, because i had to export it and delete it as explaned on the site.
Setting ID_0x709adada = 0x07f58257 InternalSettingFlag=V0
So i guess the other versions of 3DMigoto also not work. I tried 3 versions..... all 3 exact same results
The http://helixmod.blogspot.com/2013/02/chiris-force-certain-resolutionhertz.html i tried in the 32bit version cause it was explaned that this only works for 32bit games but the game crashes at startup. GameOverlayRenderer.dll and GameOverlayRenderer64.dll are deleted from steam folder so that was not the problem. I did tried to change resolution and hertz in the d3dx.ini file but it crashed aswell. :(
Also i tried 3DMigoto 1.1.36 but offcourse, did not work.
It start to feel hopeless :(
Thanks anyway for the input.....
Even the glasses i can not sell because people don't trust it.
That's also the reason game developpers don't care.
Well, i don't care also anymore. I never buy a game anymore. i use google to get a game. Yes, for free.
This is what they all deserve. thanks for the free 2D shitty games....
Very mad at people. I don't care what i say anymore, i paid for this piece of sh¡t anywayzzz.
more then 600 bucks, and for what... 2D at 144 hertz.... What a fukking joke.
3d doesn't work, so i am left with 2D games at 144 hertz...
What the hell i need a 3D monitor for. Well foek all game developpers with their selling their game with VR/3Dvision compatibility sh¡t while it's not working.
Delete this post if you want, i don't care. I tell the truth and maybe people have to listen to complainers that paid big time money for something that just don't work.
Sh¡thole world!!!!!
There are many games that work well in 3D, no need to throw a tantrum.
As far as fixing a game goes... I'd suggest not jumping right into the unknown and start off slow, look into bo3b's lessons and after that possibly study an already fixed game and/or try to fix an already fixed game.
https://forums.geforce.com/default/topic/766890/3d-vision/bo3bs-school-for-shaderhackers/
As far games in 3D game compatibility goes... there's plenty of older titles that run perfectly fine in 3D that are definitely worth replaying. On top of that there's tons of games that were fixed by the community on the HelixMod blog.
http://helixmod.blogspot.com/2013/10/game-list-automatically-updated.html
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]