- Joined
- Jun 6, 2012
- Messages
- 382
- Reaction score
- 254
- Points
- 78
- Location
- Sydney, Australia, Earth, Sol
- Website
- www.orbithangar.com
Hi All.
I am (still...) working on a long-term project, and have noticed some strange graphics behaviour. I am trying to work out what might be the cause for this:
When I create multiple instances of the same vessel with the scenario editor, delete instances, and create instances again, and place them on a planetary surface (in this case a base on Mars), for around 10 seconds or so I get these strange surface tile issues (images attached). I initially thought this must be a memory leak somewhere in my code, but I tried it with the default Delta Glider and the same issue happens (albeit to a lesser extent). This only seems to occur with the default graphics client (Orbiter.exe) and not Orbiter_ng.exe with D3D9.
Has anyone else encountered anything like this before?
Thanks all!
I am (still...) working on a long-term project, and have noticed some strange graphics behaviour. I am trying to work out what might be the cause for this:
When I create multiple instances of the same vessel with the scenario editor, delete instances, and create instances again, and place them on a planetary surface (in this case a base on Mars), for around 10 seconds or so I get these strange surface tile issues (images attached). I initially thought this must be a memory leak somewhere in my code, but I tried it with the default Delta Glider and the same issue happens (albeit to a lesser extent). This only seems to occur with the default graphics client (Orbiter.exe) and not Orbiter_ng.exe with D3D9.
Has anyone else encountered anything like this before?
Thanks all!