-
AuthorSearch Results
-
Oct 8, 2013 at 5:49pm #11064
In reply to: Skyrim , Fallout and similar
CylonSurferParticipantI am well aware of this, I think you misunderstood my post. All I am saying is that turning off shadows, although a fine temporary fix, is not a solution to the issue. HELIX managed to fix shadows for 3DVision (for free I may add) so it’s not impossible for you to do this also. Clearly, even with HELIX’s mod not being compatible with this driver it can displace and move shaders etc (even if not correctly).
From a product I have paid money for & that advertised Skyrim as a supported game I’d expect more. Beta or nay, Skyrim was stated it was a working game. Yes, it “works” depending on how you personally interpret “working” (it doesn’t CTD on launch like BioShock Infinity at least), but it is really unplayable due to the many bugs I listed above. Without working water, sky box and scaled arms I would say the game is an unplayable mess. Which is shame.
I’m not trying to have a go or anything but so far other than the edge peek function (which is liable to be copied in some shape or form) I have been quite disappointed with VORPX in general. Even as a beta I expected the listed games to at least work well considering how few there are.
I hope you are not expecting the Z-Buffer mode to carry this product as many 3D enthusiasts will not touch fake 3D with a barge pole. Take a look at all the Crysis 2/3 threads out there.
If you intend to look into these issues then fair enough, just let us know and if possible provide some kind of ETA / priority list. Equally, if intend on leaving stuff broken in games or worse still disabled (as your original reply hinted) let us know and if at all possible where / how we get our money back.
You need to seriously look at posting a bunch of known issues on your “compatible” games list so people can at least make an informed purchase.
Oct 8, 2013 at 2:32pm #11055In reply to: Bioshock Infinite
DrBeefParticipantI have the crash with both, I was running 320.49 and I updated to 327.23 to check but it made no difference.
Oct 8, 2013 at 1:11pm #11044In reply to: Bioshock Infinite
golem09ParticipantFor reference, I’m using nVidia Driver version 327.23.
Oh right, I may try another nvidia driver tonight. I still have 320.49
Do all people without crash have the newest driver?Oct 8, 2013 at 7:05am #11036In reply to: Bioshock Infinite
BadServoParticipantOn my machine, “Bioshock Infinite” is working perfectly (via Steam) for as long as I’ve tried to play it, aside from a minor head-tracking issue as described here:
https://www.vorpx.com/forums/topic/vorpx-praise-issues-impressions/
My specs are as follows:
OS: Windows 8 Professional (64-Bit)
CPU: Intel Core i7-3770K (4-Core / 3.5Ghz)
RAM: 16GB Mixed DDR3
GPU: 2x GeForce GTX 660 Ti Cards, Factory Overclocked Running in SLI
HDD: OCZ RevoDrove3 120GB PCI-E SSDI should note that I have v-sync forced off in the drivers when using the Rift/VorpX and that I’ve disabled Steam Overlay. For reference, I’m using nVidia Driver version 327.23.
@Ralf: If there’s any specific settings you’d like me to try to see if I can make it crash, let me know.
Oct 8, 2013 at 12:58am #11029In reply to: Bioshock Infinite
jasonatokcParticipantAMD FX-8350 Vishera 8core 4.0Ghz
16gigDDR3
Radeon 7970
Windows 8 64 bit
240 gig solid stateOct 7, 2013 at 9:47pm #11012In reply to: Bioshock Infinite
oogulusParticipantAlso running through Steam. Gets through logo sequence then quits out right after AMD logo. Goes back to desktop with no error messages whatsoever.
AMD FX-8350 Vishera 8core 4.0Ghz
16gigDDR3
ASRock 970 AMD SATA 6Gb/s USB 3 Motherboard
asus GTX650ti 1GB 128-bit GDDR5
Windows 8 64bitOct 7, 2013 at 2:13am #10992In reply to: Bioshock Infinite
yarvoParticipantwell in that case we are running:
i7 3770
16gig ddr3
250 gig solid state
gforce gtx 760 by EVGA
windows 7 64bitany more info i can provide?
Oct 6, 2013 at 9:24pm #10985In reply to: Bioshock Infinite
golem09ParticipantOS: Windows 7 Pro 64-bit (Avast Anti-virus)
CPU: Intel Core i5 2500k (@ 3.2 GHz)
Motherboard: msi p67a-gd65
GPU: Asus Nvidia GeForce GTX 770 Ti
Memory: 2 x 4GBSo basically everything is different.
Oct 6, 2013 at 7:30pm #10984In reply to: Bioshock Infinite
DrBeefParticipantHow 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.
Oct 6, 2013 at 1:59pm #10973In reply to: how does it work?
hugoParticipantHi thanks for the answer, unfortunately i tried the shortcut for games like skyrim, bioshock infinite, outlast, metro last light, portal 2… none of them worked. I cfan’t even access the in game menu of vorpx by pressing DEL.
Oct 4, 2013 at 12:09am #10828In reply to: Nothing works for me…
DrBeefParticipantStill 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!)
Oct 3, 2013 at 12:32pm #10794In reply to: Nothing works for me…
DrBeefParticipantIn 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.
Oct 3, 2013 at 11:12am #10776In reply to: Bioshock 1 – Geometry Mode – Lack of Depth
baggygParticipantHi 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.
Oct 3, 2013 at 6:09am #10758In reply to: Nothing works for me…
RalfKeymasterLaszlo, 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.
Oct 2, 2013 at 5:39am #10654In reply to: Nothing works for me…
LazloTheGreatParticipantSame problem here. I’ve been trying to boot up Bioshock Inf. (pretty much, the main reason I bought vorpX). Game plays fine without vorpX enabled. And Rift has worked fine on my machine. But when I turn vorpX on, it crashes Bioshock right after playing some of the opening title sequences. Every. Single. Time.
What a bummer.Here are my machine specs:
Processor
4th Generation Intel Core i7-4770s processor (8M Cache, up to 3.9 GHz)
Operating System
Windows 8 Pro, 64-bit, English
Display
27 inch LED Backlit Touch Display with IPS/Anti Glare and Adobe RGB QHD resolution (2560 X 1440)
Memory
16GB Dual Channel DDR3 SDRAM at 1600MHz – 2 DIMMs
Hard Drive
2TB 7200 rpm SATA 6Gb/s Hard Drive + 32GB mSATA Solid State DriveBP
Video Card
NVIDIA GeForce GT 750M 2GB DDR5 with TPM V1.2 -
AuthorSearch Results
