Search Results for 'BioShock'

[LazloTheGreat]

So this was interesting…

Regarding at least the Bioshock Inf. 30 sec crash:
I just installed vorpX on another rig of mine… and all is fine with BI. A main difference between it and my other machine? It runs on Windows 7, not Windows 8 with touchscreen. I’d be curious to know if others who are specifically getting the BI 30 sec crash tend to be on Windows 8 rather than 7. (Incidentally, on my windows 8 rig, I did disable the touch interface to see if that’d help, to no avail). BTW, BI is not only working through vorpX on my Windows 7 machine without a problem, but I didn’t even disable any of the other things on my system suggested in the various troubleshooting tips given. Vereio is still on the machine, all the dll files still there, etc., etc.. I didn’t have to undo any of the things suggested and this Windows 7 machine, the whole shebang was pretty much plug and play. And the game does look gorgeous. So, don’t know if there’s correllation between vorpX functionality and version of windows being used, but thought I’d put the question out there. :)

[ibminarik]

Mass Effect 3 is perfect out of the box. I cried when I saw the reapers invade, and it occurred to me that each of those buildings was full of people.
Bioshock Infinite is close, but I need to tweak the FoV some more before I’ll believe I’m there. There’s just the tiniest bit of fisheye and it bugs the hell out of me.

[DrBeef]

Still 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!)

[Aled B]

First off, thanks for everyone’s help/suggestions.

Unfortunately, having tried everything that’s been suggested several times, and having made sure there are no potentially conflicting processes present, I am still having no luck whatsoever with vorpx. I am absoloutely certain that the problem lies with vorpx; not my rift, my tracker, or my rig.

There seem to be more and more people experiencing the same issue as me with Bioshock Infinite – game crashes to desktop after 60 seconds without a crash dump or notice. Have a look at the Reddit Oculus threads, it’s developing into a common complaint.

Even when vorpx actually lasts into the game proper, I have severe headtracker issues. In 6 months of rifting, I’ve never had head movements translate into actual player character movement, but this happens constantly with vorpx. Again, I’m not alone in experiencing this.

Aliens CM still works like a charm though, so go figure!

[Ralf]

That sounds as if they stretch the scene along the view axis *shudder* . I guess, I’ll have to take a look at this, whatever it might be.

[baggyg]

Donk – thanks for the edge peek tip – that works great!

I don’t think world scale works exactly the same way since each element is only separated based upon the distance from the camera. What I find in vorpX eye separation is that quite quickly it becomes hard to focus on close elements such as the HUD. Whereas changing the world scale In Tridef seems to lengthen the complete depth without just changing the strength of 3d.

I’m probably wrong in trying to explain something by comparing a function of a completely different program. It just the easiest way I know how to compare.

I believe the complete scene needs to be “deeper” while not necessarily increasing 3D strength. The 3D actually looks fine its just that the things in the background seem to be at the wrong depth. They should be further away. If it would help I can send a screenshot taken through tridef so you can see what I mean. As I said I only have experienced this with Bioshock 1 thus far.

[DrBeef]

In 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.

[Ralf]

>> This isn’t quite the same as simple eye separation.

I’ll think about this, on first, second and third thought I would say though that scaling the world coordinates relative to the eyes visually has exactly the same effect as scaling the eye coordinates relative to the world. Math is Math, however a button is labeled.

>> Also +1 for a edge peek toggle button

Is already there. Just click the middle mouse button. click again to disable EdgePeek

[baggyg]

I tried a couple of other games and thought the 3d effect was better – Skyrim certainly looked life like in depth (in both Geometry and Z-Buffer). So perhaps its just bioshock.

“World Scale – Coordinate system scaling factor. Adjust this if the 3D separation is too strong/weak.”

This isn’t quite the same as simple eye separation.

Also +1 for a edge peek toggle button – Skyrim doesn’t seem to allow me to do many things if I have the middle mouse button pressed.

[Ralf]

Bioshock Infinite will be looked into, you’re not alone with problems in this game. Unfortunately it works for others, including me, so this is a hard to catch issue.

Did you try both the DX9 und DX11 version of FarCry3? Maybe one of them works for you. I’ll think about the error reporting once things get a bit more quiet.

[Ralf]

I’ll look into Bioshock, doesn’t struck me wrong in any way so far.

I don’t know exactly what the World Scale option does, but I’m almost sure that the result is pretty much what you can achieve by upping the Eye Separation in vorpX, which gives you a lot more 3D when you set it to the max.

[baggyg]

Hi Ralf,

Respectfully I completely disagree. Others around (reddit) have also criticised the lack of depth on bioshock (Geometry Mode) as well. The fact it is does not look like real life. Something that is 20 meters away looks like it is a couple of meters infront of me. I am not comparing it to and “over the top monitor 3D effect”. I am comparing it to another 3D driver, and whether you agree or not the other driver appears more lifelike.

I would also argue it currently feels more uncomfortable because of the lack of depth. In other solutions I can get my bearings rather easily. In VorpX my eyes are having to work hard to figure out at what depth each item is. This really does need a world scale option or the specific bioshock settings looked at. I will try a few other games and report if it is just bioshock giving me this or all vorpX.

[Ralf]

Hi baggyq,

I hope you don’t mind a copy and paste answer, it just fits too well.

In VR more 3D does not automatically means better 3D. Your reference for comparisons should be the real world not some over the top monitor 3D effect, it’s called Virtual Reality after all. :)

Usually settings are dialed in so that 3D proportions look similar to what you experience in reality. You can get ‘more 3D’ by raising the Eye Separation, but that also means getting wrong 3D compared to the real world. And vorpX on purpose doesn’t allow really extrem values, because those make the world look strangely small and lead to an rather unsettling feeling for many people after a short time.

This is no error, not even a flaw, it’s just meant that way.

[LazloTheGreat]

Thanks for your thorough response, Ralf. To answer your question, what I thought, by virtue of the last official post on the matter, was that the status of future intentions for a fix for what seemed to be described as not affecting a comparatively significant amount of users… that the status of any specific agenda to spend further time, not to mention how much, in pursuing this particular fix wasn’t quite explicitly stated one way or another yet. I know sometimes if a problem isn’t considered significantly widespread enough, it becomes counter-productive to meaningfully allocate further official troubleshooting resources toward. Not knowing you, what was already on your plate, nor where you stood on this specific tech issue, I didn’t have a clear basis to form any entitled expectation. So, rather than assume one way or another, I thought it simple enough to ask, merely to gain explicit clarification from your point of view, on the issue’s agenda from here on out, that’s all. And you just now responded to this in spades quite clearly, so, again, very much appreciated for your answer, Ralf, thank you.

I actually bought Bioshock Infinite for PC specifically for Oculus and vorpx, but otherwise my games tend to be on console. So BI was gonna be the one vorpX test case for me. I will look over the troubleshooting list again to make sure there’s nothing I’ve missed. I hope there somehow was, and it ends up being the thing that solves it. Barring that, I look forward to your future fix and enjoying your product’s bringing out that wonderful new dimension to Bioshock that so many others are currently getting to enjoy and rave about. Envy. Want to play, too.

Thanks.

[Ralf]

Laszlo, vorpX beta is out for barely three days. Of course we will investigate this. What did you think? Also vorpX beta is and was sold as beta software, which is also displayed on screen the whole time, to avoid possible misunderstandings.

I’m really sorry that Bioshock Infinite right now is not working for you. Mind if ask if other games work for you?

You may also take at look at the following general trouble shooting guide, maybe it contains something useful for you:

First and foremost: If you happen to use any DLL override (like ENB Series, SweetFX or similar) for a game you want to try: Get rid of those. There should never be any d3d9.dll, d3d10.dll, d3d11.dll, dxgi.dll, xinpunt or any other system dll override in a games directory that does nor belong there. vorpX ‘hooks’ into these system DLLs, additional overrides can create all sorts of conflicts.

The same is true for any other kind of injector (like the script injectors for various Bethesda games). They might or might not work. if in doubt, disable them.

Disable any other stereo driver you might have running (nVidia 3D Vision for example).

If in doubt, disable all programs that can show content over DirectX. Skype, Mumble, Fraps, SteamOverlay are typical cases. This should usually cause no issues, but if you have problems, it’s always worth a try to temporarily disable those programs or their in-game windows.

Same as above for Desktop Streaming Applications like Splashtop. Try to disable and see whether things work better this way

vorpX only works with 32bit application at this time. This is important for example in WoW, which also has a 64bit version. The latter will not work with vorpX.

If a game has different .EXEs for DX9 and for example DX11, try both. Usually both should work to some degree, in some cases there are hints displayed on startup which one works better. If one completely refuses to work for you, maybe you have better luck with the other one.

If you have an SLI or Crossfire (dual graphics card) system disable this. It might or might not work, but is currently completely untested an thus not supported.

Disable any graphics ‘accelerator’ (Lucidlogix Virtu for example) if you use something like this.

If you use an Intel graphics chip, you’re on your own, at least for now. System requirements for vorpX include nVidia/ATI graphics. Judging from feedback, many things seem to work with Intel, but this is completely untested. Also for some things there are distinctive nVidia/ATI rendering paths in vorpX, those things won’t work at all on Intel.

Final note: There are a games that work great for some people but cause problems for others. Nothing uncommon in the wonderful world of Windows. We are trying to resolve those issues, but fixing things that can’t be replicated consistently, is sometimes tough. There might (and will) be cases were fixing issues that apply only to some will take some time.