Jump to content

drnicolas

Frozen-Inactivity
  • Content Count

    23
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

1 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

About Me

  • About Me
    X-Plane 11.51xx; Asus + AMD Ryzen Prozessor; Graphics 1 Radeon x80, Graphics 2 Radeon

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Best wishes for the new year! I come back with this long lasting and still annoying problem: With different AMD Adreanlin drivers and trying different settings my problem has slightly imporved but still RXP GNS is unusable with the combination AMD graphics, Vulkan activated, popout mode and the RXP GNS430. Downsizing to one monitor did not change anything. Here comes my current experience: - the problem appears only with the popout mode!, never with the normal mode - Everything is fine even with popout mode as long as Vulkan is de-activated - nevertheless the fps penalty in OPENGL is massive - With some settings in Adreanlin changed, my problem improved a bit, from "popout window always black" to "heavily flickering popout window, with sometimes GNS screen apperaing for half a second", but still unusable. - I found some postings saying, that also other plugins suffer this problem. The reason should be that plugins are incompatible with Vulkan as they are drawing in OPENGL , which causes this flickering. So, question: Can somebody confirm, that using nVidia graphics cards solves this problem? Or are there some ultimate driver settings which solve the problem?
  2. Thank you. I will try it with one monitor only setup on the weekend
  3. Thank you for your questions: 1. I am using Win 10/64 with all available updates installed 2. I am using the latest RXP GNS (at least it does not offer me newer versions) 3. AMd 20.8.2 ist NOT the latest driver. But all drivers higher than 20.8.2. are blacklisted from X-plane and VULKAN is de-activated and cannot be activated. In that case, X-plane is using OPENGL. 3a. With OpenGL the RXP GNS works fine
  4. I upgraded to the latest 11.50 version of X-plane; I also have the latest RXP GNS430 version running. For a longer time I couldn't use the Vulkan feature as my AMD driver was blacklisted. Therefore I was using OPENGL and GNS was working with the GNS as part of X-plane and in Pop-out mode. I need this pop-out mode in order to move my GNS to a separate screen. Today, I went back to AMD driver 20.8.2. Now Vulkan works again, but my GNS does not. - in Popout mode, the window is black only. When moving the window around, sometimes the GNS screen content flashes for a short moment. but 99.9% the window is simply black. So, I do not see the bezel and not the screen. - when I de-activate the pop-out mode, the GNS bezel appears and also the screen content. But, sometimes the GNS disappears or flashes, sometimes it appears in front of the panel. It is clearly a problem with Vulkan. I tried with moving all graphics sliders to the far left, but no improvement. I already asked X-plane support, but they say it is a problem of the third party tool (which is RXP). Earlier this year, I already aksed for help for this problem, but RXP said, it might be a problem of X-plane. AMD not even answered my support request. So, any ideas on my problem? I need the vulkan feature to get more or less acceptable frame rates.
  5. I am using an AMD R9 card with X-Plane 11.50bxx and Vulkan. From the first beta on and still I am suffering a problem with my GNS430W: Everything works fine as long as the GNS430W is *NOT* configured as pop-out-window. Choosing pop-out-window shows me a normal Window with frame and control buttons, but inside there is only a black area - no GNS screen I can move the window around and even move it outside of the Orginal X-Plane screen. I only see randomly the GNS screen flashing for a sort moment while moving the window - that's it Changing back to non-pop-out and evrything is fine. Also my problem stops with de-activating Vulkan. Meanwhile, there have been several updates from RXP and also AMD - but no change Some say, it is a bug of the AMD drivers, RXP says contact X-Plane, X-Plane says it is a problem of the thir party developer and AMD does not answer. Am I really the only human being using an AMD card and having this problem? Ther might be a "sceret" setting in the AMD driver ?
  6. I will check, but I think I already have this driver. Using your wording, i am talking about popped-out window. Indeed, this has a normal windows border with the close-button in it. And yes, I want/MUST push the GNS430W window/screen out of the X-Plane window onto a separate screen. In fact, in the future, the GNS430W screen should be displayed on a small 3.5in HDMI-display and be mounted in my physical panel with a bezel and buttons or rotary encoders around it. At the moment - useless. It works only when the GNS430W-screen is inside the X-Plane-window and not popped-out
  7. To give a short feedback: - Only slight change - Still pop-out-window is dark, the startup screen is flashing for a short moment when moving the window with the mouse. But still not usable for me -in normal mode, flickering has improved - using 11.50b9 -latest beta adreanlin-driver - and latest RXP GNS430W
  8. I reported this bug to the X-plane developer team and got an answer. Still no improvement, even with 11.50b6
  9. Okay. The X-plane guys say "call the plugin-developer, the problem is 3rd-party related". So, i am back with a photo: - RXP GNS430W works fine as long as it is displayed non-windowed - in pop-out mode, the window is empty/black. Only when moving the window and releasing the mouse-butoon, I see the typical GNS screen for a short moment - the X-plane original GNS530 works as expected, non-windowed or as a pop-out - I upgraded to Version 2.4.19 - my AMD drivers are the latest.
  10. It is a RX460 with driver Adreanlin 20.4.1 (26.20.15029.20013. OS is Win10/64. I can try to send a video tonight,
  11. I recently upgraded a test installation to X-Plane 11.50b3 and activated Vulkan. With 11.50b1 and b2, I was not able to get X-plane up and running. With b3, i get decent 75+ fps, but after pushing back the plugin and restart, I see some strange problems: 1. GNS430 appears in the simulator window and seems to work fine 2. Changing to popout window lets the startup screen form GNS430 flicker like hell. This does not change, if I move the GNS-window out of the X-plane windoww. I have a Radeon card from 2016 and latest drivers Any good or bad experiences with Vulkan?
  12. May I try to show my expereiences. For comparison, i have a bare metal GNS430W in a Mooney. I tried several Approaches in real world: LPV - If a LPV is indicated in the EASA-Chart, then my GNS430W will show me a glidepath. LNVA/VNAV - GNS shows a glidepath and in Display LNAV+V. An example is EDQG LNAV + V - GNS shows a glidepath, but this is only advisory! The EASA chart shows LNAV only. I am not sure, but AFAIK this courtesy of Jeppesen database. An example is EDFM. Nevertheless a perfect add-on. Thanks to Jeppesen On the X-Plane / RXP GNS I see only glidepath on offcially LPV approaches. Neither EDQG nor EDFM gives me a glidepath. The database cannot be responsoble for this - it might be the firmware of the simulator. Happy Easter
  13. I am using AirManager together with RXP GNS430. AirManager also has an instrument imitating a GI106 CDI. But, it seems not to work perfect with the GNS. For example,, at startup the GNS tests the CDI showing both needles half deflected. But in my panel the CDI shows only the localizer needle defelcted. GS does not move. Perhaps, i only have to change the dataref used by the AirManager Instrument. But which datarefs is/are used by the GNS? And - does that change if you flip from VLOC to GPS? In real world, the GNS makes the lateral and/or GS-signal simply by itself from an ILS or from the GPS-derived position. Can someone helP?
  14. In real world, I can set an OBS on the CDI and the GNS430 shows the magenta/white line. 1. Set a direct-to, let's say an airport 2. Press OBS-button 3.With the OBS button you can now turn the magenta/white line as needed, for example adjust it to the runway. Same procedure is used for a holding But this seems not to work on my Sim. Is there a setting needed for this ?
  15. The "bare metal" GNS430 has support for several external Annunciators, such as GPS/VLOC MSG TERM / APPR INTEGRETY WPT Typically those are lights combined with 2 buttons like the mid-continent-annunciators. the buttons should be not the problem, as they are already supported. Are the annunciators also supported as datarefs? I do not find corresponding datarefs in X-Plane Nico
×
×
  • Create New...