So, one user alerted me to the fact, when you do the per application deployment for Starsector, and at least when using mikohime, you gotta copy the .symlinks the per application deploy creates to the jdk-23+7\bin folder, otherwise its still running the renderer on OpenGL, but the Mesa driver instead of whatever your system provides. I did get similar performance with Vulkan(tho Vulkan speeded up the loadtime from around 15 minutes to less than 5). Found this out by using rivatuner, added an text field with <APP> as the hyperlink into the overlay and it provides the renderer info.
I'll try to see if I can find the time to edit this guide this week so it provides more steps(with pictures) so less technically inclined persons can understand how to implement it.
Thank you very much. It was very complicated.
I execute the perappdeploy.cmd. I think for opengl ES and offscreen rendering I selected no. After that I copy 8 symlink files (which was created in the Starsector folder) into jdk-23+7\bin. In the Starsector folder I created a bat file which contain:
@set VK_ADD_DRIVER_FILES=D:\Games\Mesa3D\x64\lvp_icd.x86_64.json
@set LIBGL_ALWAYS_SOFTWARE=1
@set GALLIUM_DRIVER=zink
@.\Miko_Silent.bat
I don't know the function but it seems to work? The performance is very poor in main menu, but I'm sure some settings was wrong, because I don't understand the part
"how to force Mesa to use either zink or GLonD3D12" See screenshot.
My system:
Laptop 7840HS with 780M, 32GB W11.
I hope to avoid the poor AMD OpenGL performance.
Update: After I just removed the "@set LIBGL_ALWAYS_SOFTWARE=1" it seems to work fine now. No issues at the moment. Before I had 5 fps in tactical map in big battles. I will further test it.
[attachment deleted by admin]