Meant to be Seen

Whenever I try to start a game with Perception support I get spamed with this error: "The procedure entry point ??1BaseDirect3D9@@UAE@XZ could not be located in the dynamic link library d3d9.dll"
According to the FAQ I have to copy the dlls in the game folder, but it doesn't work for me.

I get this error with Perception 2.0.3 stable and 2.0.6 nightly.

I hope there is a fix for this problem

You have to put the .dll files in the same (sub)folder of the game where the main executable is.

According to the FAQ I have to copy the dlls in the game folder, but it doesn't work for me.

I tried it, but it doesn't work.

EDIT: But thanks for the fast response

paul70078 wrote:According to the FAQ I have to copy the dlls in the game folder, but it doesn't work for me.

There is a difference between just putting them in the game folder and putting them in a subfolder where the main executable is. For Far Cry they have to be in \FarCry\Bin32 for example. If you did this already and it didn't help then I can only guess that you're trying to run a game in 64bit mode.

Yes I meant that.
What du you mean with the 64bit mode? Most games are 32bit only

64 bit games probably won't work because the *.dll are compiled for 32 bit. If your games are 32 bit than this can't be the problem. Still looks like that the game is accessing the wrong d3d9.dll. Have you tried to replace d3d9.dll in C:\Windows\SysWOW64 (backup first!)?

With the 32Bit one?

Yes.

The problem is that if I replace the 64BIT d3d9.dll with the 32BIT one, the games don't start anymore. There is no error message. They simple stop from starting.
Maybe it is the best way if I compile virio perception for myself with 64Bit or is there a way to force my system to use the 32Bit directx?

Hi

For a start I am not sure I would recommend replacing any of the system DLLs in this manner. You can never be certain what you might break, and the thing with Vireio is it is an injection driver that intercepts D3D calls, but still requires the original direct x 9 to function to call through to.

WHich game are you trying to use Vireio with?, if it isn't one of the standard supported games (working on a list at the moment), then it might require additional tweaks/code changes for it to work properly.

C:\Windows\System32 contains 64bit libraries and SysWow64 contains 32bit libraries on Windows x64. Confusing, I know. If your game doesn't start anymore after replacing the d3d9.dll in SysWow64 then the problem might be somewhere else.

is there a way to force my system to use the 32Bit directx?

32 bit applications can only use 32 bit libraries so they use 32 bit DirectX already.

Error Message in Antichamber
Mirrors Edge crashes
L4D2 crashes
Skyrim crashes
Borderlands 2 crashes
Borderlands crashes

Borderland gave me a error message: Ok it seems that this error only appears with Antichamber, but the other games crash.

Could you post your specs please?, no-one else seems to have quite as serious issues as you are experiencing.

Are you able to run it without the rift in side-by-side mode?

Are you able to run it without the rift in side-by-side mode?

What do you mean?

System specs:
Windows 7 64BIT
Vireo Perception 2.0.6 nightly build
Dell Inspiron 17R SE 7720 Notebook
Intel Core i7 3610QM (4 Cores, 8 Threads)
6GB RAM
NVIDIA GeForce GT 650M (used for games)
Intel(R) HD Graphics 4000

I know that a Notebook isn't the best for gaming, but I have no problem
with this games.

Games:

Mirrors Edge:
Perception running + d3d9.dll copied:
crash
Perception running without d3d9.dll copied:
running, but ignores perception *
Without Perception and d3d9.dll
running

Antichamber:
Perception running + d3d9.dll copied:
d3d9 error
Perception running without d3d9.dll copied:
d3d9 error
Without Perception and d3d9.dll
running

Borderlands:
Perception running + d3d9.dll copied:
crash (+Screenshot in post above)
Perception running without d3d9.dll copied:
running, but ignores perception *
Without Perception and d3d9.dll
running

Borderlands 2:
Perception running + d3d9.dll copied:
crash (+Screenshot in attachment below)
Perception running without d3d9.dll copied:
d3d9 error
Without Perception and d3d9.dll
running

L4D2:
Perception running + d3d9.dll copied:
crash
Perception running without d3d9.dll copied:
crash
Without Perception and d3d9.dll
running

Skyrim:
Perception running + d3d9.dll copied:
crash
Perception running without d3d9.dll copied:
crash *
Without Perception and d3d9.dll

*(steam reports the d3d9 error twice before it starts the game)

paul70078 wrote:What do you mean?

Disconnect the Rift and set side by side mode in Perception.exe.

I test it without rift direct on my screen.

When you say:

Perception running + d3d9.dll copied

You should be copying all the dlls:

d3d9.dll
libfreespace.dll
VRBoost.dll
hijack.dll

without them all there in the game's folder, it will crash.

Sorry I wasn't presice in my answer. I copied the files:
* d3d9.dll
* hijack.dll
* libfreespace.dll

I tried to also copy VRboost.dll , but it changed nothing (mirrors edge keeps crashing)

I'm afraid I'm at a bit of a loss.. I've not seen such critical issues for so many games before, particularly supported ones (skyrim, L4D2). Is there maybe something else running that could be conflicting?, I'm honestly not sure what the problem is, your system should be ok running these games with Vireio.

I'm afraid you are going to have to play around with it and see if some other application is conflicting maybe?!

Could you run it with trace spy running to catch a debug log, that might reveal something.. possibly not, but it is worth a try.

Tried it again and it worked.

I think that the Oculus drive wasn't installed correctly and produced so the fails.

But thanks for your support

Excellent news!!, thanks for letting us know you got it working.