Recent content by jarmonik

I know the feeling. But nice work there, the documents are looking great. There are likely some outdated information but it might be easier the start fixing those after a merge.

Doesn't happen. If D3D9Client doesn't run natively on a computer then one can try installing DXVK (i.e. DirectX on Vulkan) drivers but no guarantee for it to work. There is one underlying problem that's difficult/messy to fix and I don't have time for it. Orbiter uses DllMain() for...

Anyone willing to do that ?

It's great to see that the last flight of Delta IV Heavy was a success. Good way to retire a launcher.

Nope.

Viewing an eclipse within an atmosphere is not yet supported. Currently eclipses can be viewed only from space.

Yeah, I suppose so. The problem is that Orbiter is still officially using DirectX 7 and the sample programs must work with it. After Orbiter 2024 DX7 will be removed and the vessels updated. Also it's problematic because Orbiter 2016 doesn't have full D3D9 support. So, I guess any method that...

Just to remind you that oapiGetDC() is very much obsolete, it's likely that there's no support for it after Orbiter 2024. So, HDC stuff shouldn't be used for a new add-ons.

Most likely some oapi_ call that has width and height input parameters. (uninitialized)

I don't remember the story behind those errors but you can ignore them. I will try to solve it during the coming API cleanup.

I can't find this error from D3D9Client. Have you replaced the D3D9Client that comes with OpenOrbiter with an older one ? If yes, then that's not going to work.

Graphics updates are planned for the default vessels after removal of DirectX 7 dependency. Which should happen soon after Orbiter 2024 launch. It would be great the have better meshes and textures. Also the ISS would need an update, there are some high poly ISS add-ons but they are way too...

There's been some clean-ups in a Surface API and it may effect to some add-ons if something's done very incorrectly. Is there anything in D3D9ClientLog.html with debug level 2 ? I have no idea what's going on with the scenario editor. To look into the problems I would need binaries and source...

Yeah, probably. The error also appears on /Deltaglider/Help/CMakeList.txt and many more... After reverting the root CMakeList.txt to e7477e610ff74ec5b80092437554f52b31b1f416 (Dated late 2022) it started to work. So, the problem is due to more resent modifications likely 05/02/2023, I don't know...

When trying to build the documentation, this error repeats a lot: CMake Error at Src/Module/LuaScript/LuaInterpreter/CMakeLists.txt:44 (add_custom_command): Error evaluating generator expression: $<TARGET_FILE:lua::exe> No target "lua::exe" What is this syntax supposed to mean...