Puts the Fun in Dysfunctional
All I'd say on that is that SVN handles branches very differently from git, be careful....
Same here. Zoomming in/out fixes the problem for me.Hi,
For the latest D3D9 releases (4.22-4.24) for Orbiter 2016, I get a black rendering when viewing planets at low angles at certain zooms. Older D3D9Client.dll do not give this.
Horizontal haze disable in the video settings removes the black.
Happy to do any testing of settings if it helps.
Sorry if I'm repeating something that has been identified.
Revision: 1445 Author: Kuddel Date: 2021-08-05 21:30:30 Message: Merged revision(s) 1440, 1442 from trunk: - Attempt to fix the horizon ring issue. - Planet z-fighting fix ---- Modified : /branches/2016 Modified : /branches/2016/Orbitersdk/D3D9Client/VPlanet.cpp
Yes, that should be it, Thanks. I have uploaded a new version. Since, it's hard to reproduce the problem I can't confirm if it's fixed or not. So, waiting confirmation...
Revision : 1447,1448 Author : Kuddel Date : 2021-08-05 22:47:33 Message : - bumped version to Beta 30.8 Merged revision(s) 1440, 1442 from trunk: - Attempt to fix the horizon ring issue. - Planet z-fighting fix Modified : /branches/2019 /branches/2019/Orbitersdk/D3D9Client/D3D9Client.cpp /branches/2019/Orbitersdk/D3D9Client/D3D9Client.rc /branches/2019/Orbitersdk/D3D9Client/VPlanet.cpp /branches/2019/Orbitersdk/D3D9Client/doc/D3D9Client_API_Reference.chm /branches/2019/Orbitersdk/D3D9Client/doc/Doxyfile /branches/2019/Utils/D3D9Client/build_release.bat
Maybe this? https://cmake.org/cmake/help/latest/command/source_group.htmlThere are few issues with the CMake:
- Is there a way to add a custom folder under a project in the Solution Explorer. I would like the have shader codes in that folder just like the .cpp and .h files are located in their own folders.
I am displaying my ignorance here, but I take it that shader codes are GPU scripts that are compiled at run time? If they are not listed as sources for any target in the CMake files, then they technically don't participate anyway. If they are listed, then they will participate in the build of that target, and the target will be rebuilt whenever one of the source files changes.
- Is there a way to set the "does not participate in build" flag for these files.
Not sure why that would be. Maybe your CMake scripts define additional dependencies that limit the possible parallelisation of the build process? You could also check the compiler and linker flags that CMake assigns, to see if there is anything likely to affect the time (more expensive optimisation settings?).Those can be set manually but CMake have a tendency of resetting them from time to time.
Also after moving to CMake there is a major decrease in build speed, so, any ideas how to recover it.
I've ported the flattening code and refactored it for API usage. The following pull request is rebased (and tested) on the recent main: https://github.com/jarmonik/D3D9Client/pull/1 .