Jump to content

aua668

Members
  • Content Count

    157
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

5 Neutral

About aua668

  • Rank
    Member

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    Yes

Recent Profile Visitors

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

  1. Everything is better than the ugly brown haze produced by volumetric fog. I would like to have blue fog instead 🙂 Rgds Reinhard
  2. Hi, That's he COVID19 virus which has infected the lights 😉 Do you user HDR? In that case try to reduce the Bloom factor. Rgds Reinhard
  3. Hi, In the download section you also will find older versions too. Check for this text and click for expand. Rgds Reinhard
  4. Hi, https://www.avsim.com/forums/topic/590049-adaptivesimgroupenable“-under-sim/ Rgds Reinhard
  5. Hi, Hifisim is investigating already: https://forums.hifisimtech.com/threads/8005-and-volfog.14122/#post-63037 Rgds Reinhard
  6. Hi, Aerosoft provides in the documntation folder for the A3xx a document with the title "Vol7-Thrust Lever Setup.pdf". Have you followed these instructions especially the one on page 3, where it is described, what you have to do in case you want to assign two throttle axis. Rgds Reinhard
  7. aua668

    rcbgp-50

    Hi, I have it working in 5.2. Rgds Reinhard
  8. Hi, I fly the Q400 in 5.2 without problems. I have the Pro version. Rgds Reinhard
  9. Hi, I also did experience that - but very seldom and at different locations. I had no chance to reproduce it constantly. So hard to track down. Rgds Reinhard
  10. Yesterday there was the final tennis match in Wimbledon and the final match of the European Soccer Championship - so no wonder, that nobody tested 😀 Rgds Reinhard
  11. Hi, You can save a scenario with the correct window position and use this as the default startup scenario. By that you don't have to move any window (which is indeed sometimes a problem with P3D). Especially windows overlapping two monitors are sometimes a problem. I have a three monitor setup (1x 3840x1080 for the outside view and 2x 1920x1080 touch screens for the panels. I build dynamically the startup scenarion with some parameters (airport, plane, daytime,...) in a script and then just have to startup P3D and all windows are on the correct position. Even the popup panels can be positioned by this method. A commercial product is Simstarter NG, which might be a good option for you. Rgds Reinhard
  12. The solution is also in the mentioned thread some postings below. https://www.prepar3d.com/forum/viewtopic.php?p=242281#p242281 Rgds Reinhard
  13. Hi, Definitely an improvement. Thanks! Reinhard
  14. Hi Mark, I had changed the broadcast address back from 127.0.0.1 to 192.168.1.255 to send the UDP packets to my LAN. And the phenomenon returned back. In the beginning the RemoteCDU did not work and suddenly after some time it started and did work until the end of the flight without any problem. During the first phase, where it was not working I did another test, which Majestic advised me to do: I checked, if the Q400 system control panel was working on a remote PC. The SCP uses also the UDP broadcast stream to get the information and I configured there on a different port the same broadcast mask. And it worked fine without any problem. So UDP stream from Majestic and my network seem to be ok. And if I only broadcast to the localhost address 127.0.0.1 it's also ok for AviaServer. So maybe you could check, if there is a difference receiving the packets via localhost IP or the IP address of the server machine. I have saved the Logfile. I sent you a PN, where you can download it. Rgds Reinhard
  15. Hi Mark, I have posted my problem at the Majestic forum. I got some hints, how to test, if UDP is working, if the error occurs. The last flights have been without problems and therefore I could not debug. One question: Is it relevant for your application, if it receives the UDP broadcast via the localhost interface (127.0.0.1) or via the LAN IP of the system? Normally this should be no factor but in your configuration sample I see, that you use 127.0.0.1. I had configured the broadcast mask of my local LAN segment, as I plan to read the UDP stream also with some hardware of my cockpit in future. At the moment I have switched back to localhost and since then I was not able to get the error. It obviously does work in both configurations, as I have worked with the CDU in both configurations - but maybe there are minor differences showing such side effects. Just an idea... Rgds Reinhard
×
×
  • Create New...