Page 1 of 1

the entry point in the procedure Direct3DCreate9Ex not found

Posted: Tue Oct 07, 2014 5:46 am
by user11
the entry point in the procedure Direct3DCreate9Ex not found in the DLL d3d9.dll

4 copy the dll in the folder with the .exe
OS reinstalled (not helped). DirectX reinstalled (not helped).
all run under the administrator.
error when launching any game.
what am I doing wrong?

Re: the entry point in the procedure Direct3DCreate9Ex not f

Posted: Tue Oct 14, 2014 8:51 am
by Avukatum
Hello friends!

I'm sorry for my english ..
There was the same problem that said above in games Mirror's Edge.
When working with the perception 1.1 no difficulties arise, and using perception 2.x error occurs "the entry point in the procedure Direct3DCreate9Ex not found in the DLL d3d9.dll". Copying dll in a folder with games also gave nothing ..
Used system: Windows 7 SP1 64-bit
Video Card: NVIDIA GT 635M.

p.s: Copy and replace d3d9.dll into the directory c:\windows\system32 did not help ..

What am I doing wrong? Why perception of the first version worked fine, and the second version gives an error?

Re: the entry point in the procedure Direct3DCreate9Ex not f

Posted: Tue Oct 14, 2014 11:08 pm
by cybereality
You're probably not doing anything wrong. Perception attempts to basically hack into Windows and DirectX, and this can have varying levels of success on different systems. There were lots of changes between version 1 and 2, so it's not surprising compatibility if different. Unfortunately I don't really have an answer to your problem though.

Re: the entry point in the procedure Direct3DCreate9Ex not f

Posted: Sun Nov 02, 2014 3:17 am
by paul70078
I have the problem too. Is there a way to debug it to find the problem?

Re: the entry point in the procedure Direct3DCreate9Ex not f

Posted: Mon Nov 03, 2014 5:14 am
by DrBeef
Vireio 2.0 doesn't currently appear to implement Direct3DCreate9Ex, which is odd you get this issue as I don't see this issue on my system (and neither do many others).

There is work going on to create a version of Vireio that implements all the calls and doesn't require DLL copying, this should solve the issue for you, but there's no estimated release date for that right now.