I got the VCPKG to work finally. I don't know what was the problem initially.
1) I cloned the CVPKG repository from the Git and declared env variables VCPKG_ROOT="C:\path\to\vcpkg"
2) Build "preset" was changed from "<custom>" to "x86 Release" This has never been issue before. Looks like it...
After downloading and installing LUA 5.4.2 and manually providing a path to LUA library and includes. Previous step passed, now it wants ZLIB and I can't find a place where to enter the paths.
Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22631.
Found Lua...
Out of curiosity I tried to compile this branch and got nowhere.
Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.22631.
The C compiler identification is MSVC 19.29.30153.0
The CXX compiler identification is MSVC 19.29.30153.0
Detecting C compiler ABI info
Detecting C compiler...
Recent build problems were resolved and there is a PR for it to fix it. Looks like nobody tested building Orbiter without XRSound and Documentation. Building the docs requires so-many additional tools that build must work without it.
As for the Reviews, if I want somebody to review my code...
There is a lot of LUA related work done for Orbiter 2024, does that code remain valid after update to 5.4 or does it go to garbage can ?
Also, I don't exactly like that when I got time to do Orbiter development I notice it wont compile. Since I am not a build expert it's a pain to deal with a...
Could it be that a different version of zlib.dll is being loaded for some unknown reason. So, could you check the version from a loaded modules list in a debugger. In my case it's 1.02.11.0
EDIT: You got the same version.
EDIT2: Recheck the version from the loaded modules list in a debugger
Intel has dropped D3D9 support for Iris Xe Graphics chips, so, no more native DX9 there.
You cound try to Download DXVK (https://github.com/doitsujin/dxvk/releases) and copy *.dll files in the package (.tag.gz) to /Modules/Server/ that should bring Open Orbiter back to life. I don't know why the...
If you have "Intel Iris Xe graphics" then you are likely not able to run Orbiter 2016 or older due to lack of DX9 support in that graphics chip. Open Orbiter works through DX12 wrapper (build in, but buggy) or DXVK wrapper (installation required).
Use forum search with "Iris" for further...
Could you try these modified shaders. Do they make things any better. Also the flag 0x20 uses a cheap trick to render behind other objects so top quality shouldn't be expected.
That's kinda odd. I checked the code and couldn't find anything obvious. Have you tried Sketchpad::SetWorldTransform2D() and regular TextOut() function.
Ok then, what is the code sequence used to draw the DSKY ?
SURFHANDLE hSrf = oapiGetMeshTexture(hMesh);
HDC hDC = oapiGetDC(hSrf);
That should fail. Dynamic textures do support GDI but they do not support mipmaps nor auto-generation of them on update. Only render-target-texture do.
With GDI...
There is "Enable Debug Break" check box in the config panel. It should break on violation. Also "going in DX7 compatibility mode" message is printed in the log if debug level is 2 or higher. Incorrect GDI use is the only thing that can trigger DX7 compatibility/emulation mode. Would be good...
I'll take a look at the code and see if there's something I can easily do. As far as i can tell NASSP runs very much in a DX7 emulation mode which do have limitations and stability issues. Trying to keep the DX7 emulation layer operational has already taken too much time. DX7 emulation layer is...
If you have integrated Intel Iris Xe graphics then you are having some problems running the orbiter. It's a well known problem, search the forum for solutions, lot's of threads about it.
The latest orbiter build should run much better...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.