Jump to content

fabs79

Members
  • Content Count

    46
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by fabs79

  1. Hi, I was wondering if you plan to bring your fantastic Learjet 35 into MSFS at some point? I loved it in P3D but have completely switched to MSFS now and I'd really like to fly it in the new sim. The modern business jets are not my cup of tea unfortunately, too technical, I loved it that the Lear 35 feels like a super fast GA plane rather than an Airliner.
  2. Thank you for the confirmation, sad to hear though.
  3. Sorry if this has been asked before, but I just saw that the product page for the GNS 530/430 states that it is compatible with MSFS? Can anybody confirm that it really works just like in P3D, with a 2d pop-up window that can be dragged to another monitor? I'm asking because I never read any news about it being compatible and after MSFS was released Mindstar was skeptical if the SDK even allowed for their product to be ported over to MSFS.
  4. OK, the log files only contain a few lines: rxpGNS2.gau.log contains: 17/12/27 12:51:01.667 03908 - ] # rxpGNS2.dll version 2.3.5.0 17/12/27 12:51:01.671 03908 INFO ] rxpGNSSim.dll.log contains: 17/12/27 12:51:03.938 03908 - ] # rxpGnsSim64.dll version 2.3.5.0 These are the only log files I found. Hope this can be fixed. Cheers, Fabian
  5. It's prepar3d v4. 1 in the Just Flight Arrow III and also the Tecnam P92 Eaglet by Ants Airplanes. I'll check the log file later.
  6. Hi guys, When I set up my aircraft from cold and dark, I configured my GNS 530 pop-up window to turn on when the Avionics Switch is set to on. This works as expected. But when I finish my flight and switch off the Avionics, the GNS stays on. Even when I switch off the battery the unit keeps running, which is kind of strange because there is no electricity left to power it. Any idea how I can fix this? Best regards, Fabian
  7. Has the issue with assigning button presses and keyboard commands to the GNS functions been resolved?
  8. I had the same bug, not only the keyboard commands but also the native simulator gps commands are Not working, so it is impossible to control the GNS unit with hardware buttons at the moment. Hoping for the update to fix this issue.
  9. That is great news, thank you. You just won over a new customer 😉
  10. Wow thank you, I wasn't aware of that. Then I have another question : is it possible to get the reality XP GNS unit to only show the GNS screen without the bezel and buttons? I'm asking because I have a hardware replica of the GNS 530 with real buttons, so I'd like to display just the screen of the GNS on my hardware display. Also, can the functions of the GNS 530 be mapped to hardware buttons via FSUIPC or a similar software? I don't want to have to use the mouse to control the GNS. Thanks, Fabian
  11. Hi, I just saw that you released the GNS 750/650 for Prepar3d v4. I just wanted to know if you are planning to make your older GNS 530 compatible with Prepar3d, too, because if I understand correctly the original release only works with FSX. Cheers, Fabian
  12. Hi, I just saw that you released the GNS 750/650 for Prepar3d v4. I just wanted to know if you are planning to make your older GNS 530 compatible with Prepar3d, too, because if I understand correctly the original release only works with FSX. Cheers, Fabian
  13. Is this forum still active? The last support queries didn't seem to get an answer at all. I'm not expecting an immediate solution but it would be nice to know if the issue is being worked on at least.
  14. Hi, I always had trouble getting the A2A C172 Addon to work on my system. Some instruments worked, some don´t. I´m running the latest version of Panel Builder and the C172 Addon with Prepar3d V4 and FSUIPC 5 for V4. Now I noticed that whenever I start Prepar3d, an error message appears in the FSUIPC log window: LUA Error: D:\Prepar3D v4\Modules\ipcready.lua: bad header in precompiled chunk. Could it be that a corrupt lua file is installed by the addon which causes the instruments not to read correctly? The ipcready.lua file is 4 KB big, and looks a little strange when I open it with an editor, lots of strange ASCII symbols with some text in between, not like other lua scripts I know. Thanks, Fabian
  15. Hi, I recently built a panel with a Heading Indicator as the main navigation gauge (my earlier panels all used a HSI); now I noticed that the Heading indicator doesn`t react to the "gyro drift" input from Prepar3d V4. When I push the "gyro drift inc" or "gyro drift dec" buttons, the dial doesn`t work. The only thing that I can move is the heading bug, but the dial should move too, to account for the gyro drift error which FSX/P3D simulates when the option is checked in the realism settings. When I look at the virtual cockpit, the dial moves correctly to the button inputs, but the movement is not made by the panel builder gauge. I tried both the HeadingIndicator and HeadingIndicatorC172 gauge, but none seem to work. Any ideas? Thanks, Fabian
  16. I can tell you that in my case the culprit was a file called apcontroller.exe that caused the Sim to crash. It is part of some Aerosoft sceneries like Split or Prague and adds an entry to the exe.xml without notice. Deleting this entry solves the issue. Took me weeks to find out. Maybe your problem is the same. Cheers, Fabian
  17. Reinhard, the ipcinit.lua file is present in the FSUIPC folder and I´m using the A2A interface, so that´s not the cause. Is there some kind of program that can test the connection between the gauges and the simulator? To see if data is sent to the gauges? And I´ll try the simconnect installation the next time I´m at my PC.
  18. Hi again, sorry to bother you again,but I encountered some issues with the A2A C172 panel builder Addon. A few months ago I had some trouble getting the A2A instruments to work over a network, back then I started this thread: http://www.avsim.com/topic/491410-can%C2%B4t-get-the-a2a-c172-panel-builder-addon-to-work/ The problem resolved itself somehow without me knowing what I really did. But now, after some changes to my system (updated to Prepar3d 3.4; reduced some overclocking settings due to heat building up, installing and uninstalling a few aircraft and sceneries) the A2A gauges start acting up again, This time it´s a little different though: some gauges still work: the Altimeter, Clock, Flaps Indicator work flawlessly. Others still react to the simulator but with a distinct lag: the Attitude indicator, Heading indicator and Turn indicator only update every few seconds. And then some gauges stopped working completely: the Airspeed indicator, Fuel gauges, Fuel Flow and EGT and some others don`t react at all. So I´m at a loss what to do next: I already redownloaded, uninstalled and reinstalled the Addon and interface, added exceptions to windows firewall - without luck. My network is not using a Wifi connection (the two computers are linked to a router with LAN cables, and the standard PB gauges are working, so it´s not a network problem). And this time the A2A gauges show the same issues even when I run them on the same PC as Prepar3d. So does anyone have an idea why the gauges are acting up like this? Is there a way to see what data is transferred between the two computers? Thanks again, Fabian
  19. Although I already posted this a few threads below, just to put it into its official place: Addons for the A2A C182, A2A Cherokee and Aerosoft Twin Otter would be most welcome. Thanks, Fabian
  20. Works perfectly in Prepar3d V3.1 and 3.2. After all it`s just a VGA monitor and a row of buttons emulating a Joystick which is then assigned via FSUIPC Cheers, Fabian
  21. OK I´ll try this. The only thing I´m not sure about is how to know if an event is unused to avoid conflicts. OK I tried this method but unfortunately the problem persists: Though I can trigger the event with the custom control set, it only works once. When I press the button a second time, nothing happens. What am I doing wrong? Is there a certain parameter to set? Do I need to set a parameter if the button is released? Sorry to bother you, but I´m really confused.
  22. Hi everyone, I hope you can help me out. I´m trying to map the hardware buttons of the Emuteq GNS 530 to the Mindstar GNS events using FSUIPC offsets. I tried to use Keyboard mappings first but this didn`t work very well, because the GNS window has to be "in focus" for the buttons to work which is not always the case on a multi-monitor setup. So the FSUIPC method seemed more reliable. However, I´m at a loss how to make this work. I understand how to assign unused offsets to specific functions in the GNS.ini, which look like this now in my setup: [KEYBOARD] GPS1_COM_VOL_PRESS=FSUIPC:0x5300 GPS1_NAV_VOL_PRESS=FSUIPC:0x5301 GPS1_COM_FREQ_TOGGLE=FSUIPC:0x5302 GPS1_NAV_FREQ_TOGGLE=FSUIPC:0x5303 GPS1_LARGE_CV_INCR=FSUIPC:0x5304 GPS1_LARGE_CV_DECR=FSUIPC:0x5305 GPS1_SMALL_CV_INCR=FSUIPC:0x5306 GPS1_SMALL_CV_DECR=FSUIPC:0x5307 GPS1_SMALL_CV_PRESS=FSUIPC:0x5308 GPS1_CDI=FSUIPC:0x5309 GPS1_OBS=FSUIPC:0x530A GPS1_MSG=FSUIPC:0x530B GPS1_FPL=FSUIPC:0x530C GPS1_VNAV=FSUIPC:0x530D GPS1_PROC=FSUIPC:0x530E GPS1_RANGE_INCR=FSUIPC:0x530F GPS1_RANGE_DECR=FSUIPC:0x5310 GPS1_DIRECT_TO=FSUIPC:0x5311 GPS1_MENU=FSUIPC:0x5312 GPS1_CLR=FSUIPC:0x5313 GPS1_CLR_HOLD=FSUIPC:0x5314 GPS1_ENT=FSUIPC:0x5315 GPS1_LARGE_GPS_INCR=FSUIPC:0x5316 GPS1_LARGE_GPS_DECR=FSUIPC:0x5317 GPS1_SMALL_GPS_INCR=FSUIPC:0x5318 GPS1_SMALL_GPS_DECR=FSUIPC:0x5319 GPS1_SMALL_GPS_PRESS=FSUIPC:0x531A GPS1_RAIM_PREDICTION_FAILURE_TOGGLE= GPS1_RAIM_ACTUAL_FAILURE_TOGGLE= GPS1_FAIL_GS_TOGGLE= GPS1_FAIL_GS_SET= What I don`t understand is how to trigger those offset functions within the simulator with a hardware button. According to the Mindstar guide to the gns.ini, "The GNS expects the offset to be an integer in the range of 0 to 255. Each time the value at the specified FSUIPC offset increments, the GNS will execute the specified function" So the correct method within the FSUIPC button assignment should be to set the hardware button to perform the FS control "Offset UByte increment" with the parameter set to 1 because this should increase the value of the offset by 1. However, when I push the button nothing happens. The only way I can trigger the event is to use "Offset Byte Set" and set the parameter to 1; this allows me to use the button a single time. But the second time I push the button, nothing happens because the Offset stays at 1 and doesn`t increase any further. Does anyone know how to set this up correctly? Thanks in advance, Fabian
×
×
  • Create New...