As for VSYNC: We saw that the default AMD driver setting is to always OFF for VSYNC in our case. Setting this switch to application controlled enables VSYNC with Aerofly and OpenGL.
Posts by admin
-
-
As for VSYNC: We can confirm its not working on our side as well which is strange as we basically follow sample code to enable/disable VSYNC.
Anyway, for now you need to use OpenGL on AMD cards until we find out more. As for VSYNC we will analyze this more.
-
RiseT: We do have a RX 580 for testing now and can reproduce the crash. But after looking at it for quite some time we have no single clue on whats causing the issue. It would be great to get some support from AMD here, but the chances are low.
As for OpenGL VSYNC: The next version on Steam will output some more debug information for us, but we can't see what we should be doing wrong. Double check you haven't overwritten anything inside your 3D graphic card driver settings.
-
The setup you want to achieve is currently not possible. The y-value has nothing to do with your position inside the airplane, its just a position on the screen. Using the separate view list all you do is open up new rectangular areas on the screen and show the Aerofly content on it. You can't at this point set the real position inside the airplane, its somethings we would have to program first.
-
You need to describe in more detail what you try to achieve with the 3 screens. We can then say if this is possible or not.
The Y-axis is simply moving the position of the view up in the window, its probably not what you want. If you want to align the 3 screen better, please play with the rotation angle ( use something less than 45 degrees ) and also play with the field of view.
As for removing the wings and struts, this is not possible.
-
NE-76: Mehr Details bitte. Grafikkarte, Vulkan oder OpenGL, Treiberversion und bitte ein Screenshot. Am besten neuen Thread öffnen.
-
You will get an answer from jetpack soon, but this is normal on constant speed props.
@jetpack: Please lets put a good article in the Wiki about this.
-
Sorry, the animations were indeed broken, it should be fixed now.
-
Ok, the fix is now live, please try it on your side.
-
Ok, this was indeed a bug in our latest version. We have fixed it internally and will publish an update today or tomorrow.
One warning: Running this with 3 separate views has a huge performance impact, do not expect good performance with this setup.
-
Bilder werden wenn ueberhaupt nur aus Copyright Gruenden geloescht. Betreff der Lichter schauen wir uns die Sache noch einmal genauer an, so dass die beiden Arten der Beleuchtung besser zueinander passen.
-
Please post your main.mcf here and show us a screenshot of Aerofly so we can see whats wrong.
-
RiseT: Ok, thanks for trying all this. We might have to try this card ourself to see where this issue comes from.
-
@Ed: Could you please send us the file tm.log and a download link for this scenery to mail (at) ipacs.de, so we can have a look at it?
-
Well, we tested with all on Ultra, thats why its a little strange. You are right the 560 is quite a bit slower.
-
RiseT: This is strange. It doesn't explain the two warnings we see. We have tested with 18.5.1 and a RX 560 and it runs fine. Any chance you try that driver?
-
@RiseT: Are you sure you have installed the latest AMD driver from http://www.amd.com? According to the tm.log you sent there are two issues that indicate the wrong driver or a missing feature. We have tested a Radeon RX 560 Series and that one works fine. Please reduce quality settings as a test and choose a location with only few airports around.
-
Cultivation files can now reference our XRef objects like this:
Code
Display More<[file][][] <[cultivation][][] <[string8][coordinate_system][lonlat]> <[list_vegetation_map_exclusion_zone][vegetation_map_exclusion_zone_list][] > <[list_plant][plant_list][] > <[list_building][building_list][] > <[list_light][light_list][] > <[list_xref][xref_list][] <[xref][element][0] <[string8][name][test]> <[vector3_float64][position][-123.001606 44.907438 0]> <[float32][direction][93]> > <[xref][element][1] <[string8][name][C172_livery1]> <[vector3_float64][position][-123.001606 44.907438 0]> <[float32][direction][95]> > <[xref][element][2] <[string8][name][C172_livery2]> <[vector3_float64][position][-123.001606 44.907438 0]> <[float32][direction][185]> > <[xref][element][2] <[string8][name][UH60_usarmy]> <[vector3_float64][position][-123.001606 44.907438 0]> <[float32][direction][275]> > > > >
-
The Vulcan / Oculus rift blank screen might be linked to the NVIDIA drivers that are installed as part of the Windows Update procedure. We recommend to download a dedicated NVIDIA driver from http://www.nvidia.com and install it. This should fix the issue.
-
sylvain: The GTX should be Vulkan compatible. Maybe send us the tm.log file right after you tried enabling Vulkan.
For developers we also have the developer camera enabled without hacks in the main.mcf. Press CONTROL+F8 to enable this camera. Hold left mouse button and move mouse to look around. Use 'W' and 'S' keys to move around. Press 'R' to go close to the airplane again.