Printable View
Have you guys tried with the NVIDIA 275.33 driver version? It could be that other driver versions don't like the combination of recent RIFT optimizations and IS hijacking all D3D calls to display the IS overlays.
Also, it could be interesting to see if you guys also have problems with FRAPS, since it does a similar D3D-hijacking as IS does?
Quote:
Originally Posted by Smedbox
I'm having the same problem on a laptop with a radeon 5800. Don't think its just a nvidia issue. The other 4 computers run just fine.
I've tried everything easy i can think of. Stuff like turning off addons, and removing the files in the interface folder. I was able to dupe the crash a few times by loading different interfaces.. ie /loadui 5box. It doesnt always crash when i mess with that though.
Not sure what else to do, the game runs fine when i don't launch with isboxer.
I am running an ATI Radeon 5870. So not NVidia here either.
I have not played with no Overlay, though I can't imagine that being an issue.
Yeah, it's not an NVIDIA-only issue, but that doesn't mean that it's not a graphics driver issue. It does make it much less likely, but there can be some bad interference between IS DirectX-hooks and the DirectX usage of the game, which certain driver versions could be more tolerant to than others.Quote:
Originally Posted by notole
When IS is enabled, all graphics drawing from the game is diverted from going straight to DirectX and the driver. Instead, all graphics function calls will go to IS, which then forwards the calls to DirectX and the driver. IS will modify some of these function calls and add it's own drawing at the end of every frame. FRAPS does this too.
Yeah I understand driver issues. Was only mentioning that I dont have NVidia.
Turned overlay stuff off and crash still happens. Not a big surprise there.
I have not tried Octopuss. Maybe I will try that until the issue with ISBoxer gets figured out.
See above with regards to NVidia vs ATI -- I have one box with each type of graphics card and are (with the exception of the disk subsystem) identical in CPU/motherboard/RAM/etc..Quote:
Originally Posted by Smedbox
Hmm...an interesting thought. I don't have fraps but I may download the trial version and see what it does.Quote:
Originally Posted by Smedbox
I'm working on tracking this down, but when I kill rifterrorhandler.exe and attach a debugger I'm not getting any crashes. And of course, the rift error handler won't share any of its information it will only send it to Trion and there doesn't seem to be a log of it.
So... if anyone wants to try killing the rifterrorhandler.exe processes (there is one per instance of rift.exe) and see if the crashes stop for them too... report back ;)
Quote:
Originally Posted by Lax
I will do that now. After my test with older ati drivers fails.
I'll give this a shot when I get home tonight.Quote:
Originally Posted by Lax