Forum Replies Created
-
AuthorPosts
-
DrBeef
ParticipantI have also had success with the cracked version of BI (no guilt as I own the full version through Steam).
It is strange how, if this is a DRM issue, it affects some people and not others. However this certainly seems to be the best explanation as it is now working on my machine without fault, whereas before it would crash after 30 seconds every single time.
DrBeef
ParticipantNo such luck for me, I’ve tried all the settings in vorpX config utility and nothing works. Still crashing after a short period if time.
DrBeef
Participantoh.. exactly like @jasonatokc just did too..
DrBeef
ParticipantI attached a debugger and though I couldn’t get a stack trace, I did get a list of loaded modules at the time of the crash, which I sent to the the support email address.
If anyone else who is having the crash is able to do that, then perhaps it might help spot something consistent on our crash prone rigs in what is currently loaded into the process space at the time the issue occurs.
It’s another wild stab in the dark, but at least it is something to try (if you can), and it might yield better results than the machine specs, which don’t appear to have revealed anything.
DrBeef
ParticipantI had Asus GPU Tweak installed, I exited that, but still get the crash. MY card is overclocked by default, so I don’t know if that might have something to do with it or not?!
Pretty much clean out of ideas at this point.
DrBeef
ParticipantI’ve not tried turning vsync off yet, will try that later (when I get home), though I don’t have much hope it will make a difference.
DrBeef
ParticipantI have the crash with both, I was running 320.49 and I updated to 327.23 to check but it made no difference.
DrBeef
ParticipantMine is the “30 seconds” crash, doesn’t matter whether I make it as far as gameplay or just leave it to load up the title sequences, after approximately 30 seconds it just drops out to the desktop. Sometimes I get the windows dialog that says “Bioshock Infinite has stopped working…”, other times I get nothing, just a crushing sense of disappointment.
DrBeef
ParticipantHow about everyone who’s getting this issue shares their rig’s specs, just in case we see a correlation that might assist Ralf in resolving this issue?
I’ll start…
OS: Windows 8 Pro 64-bit (Windows Defender Anti-virus)
CPU: Intel Core i5 4670k (@ 4.2 GHz)
Motherboard: Asus Z87-K
GPU: Asus Nvidia GeForce GTX 660 Ti Top (OC’d to 1157mhz)
Memory: 8GB Crucial Ballistix Sport PC3-12800 (2 x 4GB)
Wireless Mouse + KeyboardvorpX works fine for everything else I’ve tried, it’s just BI that has an issue.
DrBeef
ParticipantI’m just using “comes free with windows” Windows Defender, and disabling it made no difference. However it occurred to me earlier that despite thinking I’d tried everything, I am not sure I have actually disabled the Steam overlay, so I’ll give that a go later to see if that makes a difference.
DrBeef
ParticipantStill no luck with Bioshock Inf. I’ve run out of ideas, updated nvidia driver to 327.23 (or something like that), re-installed vorpX, rebooted countless times, checked to make sure nothing else is running.
Each time the game starts and lasts approximately 30 seconds (i’ve timed it), if I click through the titles at the beginning I can sometimes get a few seconds of gameplay before it just CTDs, enough of a teaser to make it all the more frustrating, it’s nothing to do with my game save since I can get as far as in game. It is like vorpX is causing BI to expire after about 30 seconds whatever is going on. Nothing in the windows event log though.
Very odd (and disappointing!)
DrBeef
ParticipantIn my desperation to see Bioshock Inf. running on my rift, I am going to update my graphics drivers to 327.23, just in case that makes a difference. I’ll try this evening and report back.
I have a pretty vanilla system, with no additional injectors (I’ve made sure TriDef isn’t active) or directX dlls lying around, anything else like that going on, so I am struggling to see where the issue might lie. Attempts to attach a debugger to the bioshock process just saw it freezing, so I gave up on that for now.
I’ve provided vorpX support with my save games and some crash dumps, just in case they can use them to figure out this issue.
DrBeef
Participantvorpx binary that is.. obviously you wouldn’t have a bioshock binary with debug symbols or instrumentation
DrBeef
ParticipantRalf
I’ll zip up my save game folder and mail it to the support address just in case you are able to use that. There are also some crash dumps in the BioShock Infinite binaries folder, so I’ll chuck them in.
Incidentally, I am using a wireless mouse and keyboard, so will retry with both wired later too, just in case. I’ve not given up yet.
Also, if there’s anything you want me to try (do you have a binary with any debugging or logging that I could drop in?) I would be happy to help get to the bottom of this with the little spare time I am allowed by family commitments.
DrBeef
ParticipantI’m seeing exactly the same behaviour with Bioshock Infinite, which was my main reason for investing in the Beta unfortunately.
The game starts, but I don’t get as far as game play, it just Crashes to Desktop while trying to load my saved game. I am loathed to see if it is the game load that is part of the problem, as I am half way through already and don’t really want to start again (and when I move the save game files to a safe location, Steam just puts them back again).
I tried Skyrim, and that works wonderfully. I also tried Crysis 3, which does work as well, but I can’t set the FOV high enough for it to really be playable on the rift. I’ve not tried anything else, it was really only Bioshock Infinite I was keen to play.
I’ll try to do some more experimentation tonight, but multiple restarts, stopping everything else running, including Windows Defender didn’t yield any success.
-
AuthorPosts