@Jarmonik: I've tried the "Debug-Builds" you've posted (Post 4713) and they seem a bit odd...
Did you build them from the HEAD revision of SVN? Or are there any local changes included?
No, there are no local changes. It's a regular build I always use for testing and development. Using the project files stored in SVN.
But, I did resently update my DirectX SDK from February 2010 to June 2010. D3D9Client version 3.4 is the first one build with June 2010 setup.
There is also a new build of the gcAPI.lib. Build with visual studio 2008. I tried to include a debug build of the gcAPI_dbg.lib in debug build of the client but I got some weird errors. So, a release build of gcAPI is incuded instead like is always has.
Another point: It looks like you do not have the most current version of Visual Studio
(VisualStudioVersion = 14.0.25123.0 vs. VisualStudioVersion = 14.0.25420.1). Maybe an update of VS is a good thing...
I don't expect the VS update to do the trick, but that update (Update 3) is the stable version for quite a while.
Thanks about leting me know. I thought it would auto-update like everyting else these days.
If I had to guess, I would blame a Runtime-Library mixup (static vs dynamic) to be the cause for Wolf's issues.
Shouldn't it effect everybody in a same way ?
---------- Post added at 18:34 ---------- Previous post was at 18:23 ----------
the debug description does not seem to be useful to jarmonik so I do not know what I can do to make the latest release working on my end..
I would essentially need the Fault offset and Module information, so that I could look at the source code at that location.
Faulting application name: orbiter.exe, version: 0.0.0.0, time stamp: 0x57c23356
Faulting module name: D3D9Client.dll, version: 3.4.0.0, time stamp: 0x5c224375
Exception code: 0xc0000005
Fault offset: 0x0004b1f4
Faulting process id: 0x31a4
Faulting application start time: 0x01d49c6298d7d792
Faulting application path: C:\Software\Orbiter2016-Official\modules\server\orbiter.exe
Faulting module path: C:\Software\Orbiter2016-Official\Modules\Plugin\D3D9Client.dll
Report Id: e0703dde-1c71-47ba-99ff-854f9480607b
Faulting package full name:
Faulting package-relative application ID:
Also a screen shot from the debugger showing the Callstack and disassemply of the fault location would be helpful.
---------- Post added at 18:59 ---------- Previous post was at 18:34 ----------
Wait a minute, There was an issue that might explain the problem.
Latest Docking Camera release for Orbiter 2016 is infact a debug build. Where as the build for Orbiter Beta is a release build. My compiler refused the compile a release build for O2016 and I did not have time to start investigating the problem so I made a debug build instead. So, does it now require a debug runtime libraries ?
edit: No, the runtimes are statically linked.