Search results

Not the same but something is wrong in there, I can see a major difference, Thanks. Will look into it...

So far. I haven't been able to reproduce the problem with stock vessels.

There is yet an other problem that at-least DX12 device can't be created in DllMain(), which is unfortunately used for device creation in Orbiter 2010 and 2016. If that limitation applies to DXVK as well then, I don't see any way to run those Orbiters with such hardware. I don't see anything in...

Yes, of course, if the requested level is not the highest existing level then that would have caused the code to fail. How could I over-look something like that. Good catch. I am little confused about (qlvl + 4) why the "+ 4" since, the initial for loop is " for (lvl = reqlvl; lvl >= 0; lvl--) "...

Can't you just flatten the main elevation under the launchpad ? (in the furute) 1. We have Elev.tree 2. which is overridden by /Elev/ files (*.elv) 3. which are overridden by Elev_mod.tree 4. which is overridden by /Elev_mod/ files (*.elv) For the tile textures we only have Surf.tree which is...

I have been watching the code trying to find the problem but no much so-far. In a cache, Elev_mod information is applied to a main tile and then cached. So, evev_mod doesn't require a separate cache. I noticed that "LoadElevationTile_mod (lvl+4, ilat, ilng, elev_res, t->data);" was applied...

Intel has dropped D3D9 support for Iris Xe Graphics chips, so, no more native DX9 there. Download DXVK (https://github.com/doitsujin/dxvk/releases) and copy *.dll files in the package (.tag.gz) to /Modules/Server/ that should bring Orbiter 2010 and 2016 back to life via D3D9Client. I don't know...

Ok, thanks for tracking it down. What opinions there are about the elev_mod, do we really need two elevation layers ? It's a little messy.

Yes, Images and textures are binary files as well. Of course, it would be better if the Git's build process could automatically include the debug-libs in a zip packages but I have no idea how to do that and I don't have time to start looking into it. I don't see problem in building them manually.

CMake adds more complexity to a build process. If we have someone new with little knowledge of build processes then it could be overwhelming. I don't know CMake all that well either. Even if new VS versions comes with a high rate the old project files still opens and works. If I recall VS 2019...

Also, could we simply copy "tileedit" binary from Orbiter 2016 and add it to the repository, no need to include Qt ?

What should we do with the SDK Samples, the code files are in place but there's no project files to compile them ? Should there be some easy way the compile them without compiling the Orbiter, or are the code files enough ?

Thanks for the report, problem should be fixed now.

I'll try to fix that in some point in the future.

Ok, that should be fixed now. I noticed when the camera was moved to a distant body, previous body becoming inactive the tiles were not unloaded. A second problem much more trickier was found when zooming to a planet's surface from a low orbit (i.e. narrow FOV 10deg). Tile resolution is...

There is a new commit, is the problem fixed ? There is still a memory leak somewhere causing the process memory to jump about 20-40MB each restart from a launchpad.

The problem must be the screen size, it's somehow causing surface tile density to become very high. The VEXTEX_2TEX[] in your case appears to be around 258 MB, mine remains below 50 MB. What are the display's pixel counts ? I ran a successful over night test on 30x30 lunar orbit. Memory climbed...

It would be nice to be able to see something in the screen shots but I get the picture. Currently, the system memory data cache doesn't release memory when exiting back to launch pad, it's kept pre-allocated for the next run. It was easier implement that way. But I can make it to release the...

One possible reason is to keep the API simpler, where as the internal data structures can be more complex. I don't really see any problem keeping them separated. I don't recall the internal data structures ever been exposed to end user. I made my fist add-on somewhere in 2003-2005

I ran a test with these configurations. Frame rate was about 2.1 fps. There is a small constant increase of system memory consumption. High-res textures installed, 90deg fov down to moon. Resolution bias at max. In your case how does the memory climb to 1.7G ? Could you give a plot from...