Search results

(y) Panel still stretched.

This change works, "kinda". The click points are not correct and the arrow keys moves the MFD. Top Hatch looks like this with your new change. And Fullscreen..

TexFilms has many tutorials on YouTube.

4k Resolution Max Window. When I try NASSP I get these errors OGLClient::clbkScaleBlt tgtx=0 tgty=0 tgtw=3840 tgth=2024 OGLClient::clbkScaleBlt srcx=485 srcy=0 srcw=2580 srch=1360 Segmentation fault (core dumped)

At the moment you have two options. First, you can maximize the Orbiter window while playing, but you cannot hit easy the buttons that are accessed with F4 in Orbiter. Second, you can maximize the orbiter window before starting a scenery, then the buttons are small but you can hit them. This...

Maybe this can help you for now https://www.orbiter-forum.com/threads/linux-playground.40476/page-2#post-595553

I had the same transparency problems. The solution was to place the meshes with transparent parts at the end of the scenery. In the meshes themselves, the transparent groups should also be placed last in the mesh.

I have no idea, maybe @jarmonik can give you a better answer.

All buildings have shadows in D3D9

How do you do that?

Zooming Rotating no clipping at all. (y) Next bug, after the S-IC separation, you are moved backwards in the VC, so that the VC is far ahead of you. Speaking of submodules. When compiling, a file named "UCSO" is created in "/orbiter_linux/orbiter_test/orbiter/build/Orbitersdk/include" and...

Nice find. It works. Antialiasing turned off in NVIDIA Settings, no seams artifacts. But I discovered another BUG. If I zoom out, in the outside view, then clipping occurs. For example, here in the NASSP scenery "Apollo 11 - 02 - Before Launch T-30sec.scn" flight time 115sec. See screenshot.

@Gondos I installed the xorg drivers for testing, same problem, without antialiasing the seams are visible.

That's it. Just have the feeling that it is a bit slower, which is also to be expected. Edit: Commenting out the line again and selecting "Override Applications Settings" in the NVIDIA configuration and setting the antialiasing higher than 0 also helps.

Yes, that solves the problem. I don't know why it didn't work before, because Windows only uses 16 bit. @Gondos Pay attention to the buttons in the top left, if you enlarge the window immediately before the scenery is started, the buttons are clickable. This can be used as a temporary solution...

Here is a screenshot comparison D3D9 and OpenGL Edit: The seams between the faces appear to be transparent.

Doesn't work. Parts of the LUT are still missing. By the way, in the file "orbiter_test/Orbiter/Config/ProjectApollo/Earth_VirtualAGC/Base/Canaveral_VirtualAGC.cfg" you can delete the part at the end between BEGIN_SURFTILELIST and END_SURFTILELIST or the whole part, then the black areas at Cape...

@Gondos NVIDIA GTX 1060 6gb D3D9 also uses 16bit, which should be enough and Orbiter in Windows has no problems with it.

@Gondos 1st. I have these wireframed faces. Is there a solution for this? 2nd. Parts in the LUT mesh are missing. Is there a limit number of vertices or faces?

..... Error creating directory "/home/matias/orbiter_test/Orbiter/orbiter/build/Orbitersdk/include/UCSO". ..... There is a file with the name "USGO" in this folder and so no folder "USGO" can be created in that directory. This file is a C++ source code. Rename it to "UCGO.cpp" and try again...