fabs79

Great news, Thank you!

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.

Thank you for the confirmation, sad to hear though.

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.

Ok I'll try that

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

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.

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

Has the issue with assigning button presses and keyboard commands to the GNS functions been resolved?

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.

That is great news, thank you. You just won over a new customer 😉

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

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

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

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.

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

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

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

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.

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

OK now, something strange has happened. The A2A C172 is working now! And here`s what I did: nothing! I don`t know how this happened, I didn`t change anything in my setup. After a few days in which I hadn`t had time for flightsimming I started up Prepar3d and thought I´d give it another shot. Fired up the A2A C172 PB on my secondary PC, connected the Interface and suddenly the gauges came to life. I don´t know what was wrong all the time, must have been some stupid mistake on my side, but anyway I´m happy now. Keep the Add-Ons coming!

OK thanks, I´ll write you an email then. Any way to narrow down the problem beforehand? As I said, no error message is displayed when the crash occurs, but maybe there`s some kind of log file I don`t know about so I could provide additional information.

OK, unfortunately the Network and Sharing Centre in my Windows 7 Version (64 bit Home Edition, German version) looks completely different than shown in the link provided above. Though I can see a list of my network adapters (it shows my Wireless adapter and the LAN), I don`t even have an "advanced settings menu" where I can change the adapter order. I can enter the advanced settings of each adapter separately and change things like TCP/IP protocols, IP and DNS and loads of other things I don´t know about, but no window looks like the one in the FAQ section of your homepage. I guess I´m ready to give up by now - I just don´t know my way about the details of setting up windows networks, the last network I set up was a 4 PC LAN under DOS 5.1 :smile: I still don´t get why the standard version of PB and the Dodosim Add-On worked out of the box without me even once having to enter the network setup, but the A2A Add-On doesn`t . somehow it seems to handle data exchange differently. I guess I have to find a way to connect the display I use for the instruments to my main PC when using the C172 and to my secondary PC for all other planes, although that has several disadvantages (eg Prepar3D menu options don´t work correctly when a USB monitor is connected to the PC on which Prepar3d is running; this was the main reason I went for the network approach in the first place). But still, thanks for your support and your patience. I´ll keep recommending Panel Builder on other forums, it`s still the easiest way to build an instrument panel without spending thousends of dollars. Cheers, Fabian

Hi guys, I know there are other threads concerning my problem, but I haven`t found and answer yet so I thought I´d create another one. I still can`t get the Mindstar GNS 530 to work properly in P3D V3.3. I have an Emuteq GNS 530 hardware unit and use it in conjunction with your GNS 530 software. I set up the Emuteq hardware buttons to their according GNS functions using FSUIPC offsets in the GNS.ini, and I installed the Mindstar GNS 530 unit into my Lancair Legacy panel.cfg (and some other planes, too). The buttons work as expected, however whenever I try to enter a waypoint on the FPL page of the GNS 530, Prepar3D freezes for a few seconds and then crashes to desktop without any error message as soon as I push the "ENT" button. The same happens when trying to use Direct-To-NAV. I can use the rotaries to enter an ICAO code, but as soon as I push ENT to activate the Direct-To-NAV - freeze and CTD. I tried re-downloading and reinstalling the GNS software a few time now, updated the Prepar3D client to the latest version (3.3.5) but still no luck. My panel.cfg for the Lancair Legacy looks like this (note that I only use a 2D window, no virtual cockpit unit): // RealAir Legacy 2012 [Window Titles] Window00=Main Window01=GPS Window02=Blank [VIEWS] VIEW_FORWARD_DIR=0.000, 0.000, 0.000 //-------------------------------------------------------- [Window00] size_mm=1024,1024 position=0 BACKGROUND_COLOR=0,0,0 visible=0 ident=15552 //-------------------------------------------------------- [Window01] size_mm=456,331 window_size=0.5 position=8 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=GPS_PANEL gauge00=MPI_GNS!GNS530_nobezel, 0, 0, 456, 331, 1:1:225 //-------------------------------------------------------- [Window02] size_mm=1,1 position=0 visible=0 ident=15600 BACKGROUND_COLOR=0,0,0 gauge00=RASLegacy!Blank, 0, 0, 1, 1 //-------------------------------------------------------- [VCockpit01] size_mm=1024,1024 pixel_size=1024,1024 texture=$RASLegacy_CFG background_color=1,1,1 gauge01=Config!Options, 1020, 1023, 1, 1 gauge02=Config!RealView, 1021, 1023, 1, 1 gauge03=RASLegacy!InitVars, 1022, 1023, 1, 1 gauge04=RASLegacy!1hzCode, 1023, 1023, 1, 1 gauge05=RASLegacy!2hzCode, 1024, 1023, 1, 1 gauge06=RASLegacy!18hzCode, 1025, 1023, 1, 1 gauge08=RASLegacy!NavCom1, 1, 2, 509, 61 gauge09=RASLegacy!NavCom2, 1, 64, 509, 61 gauge10=RASLegacy!ADF, 4, 127, 332, 49 gauge11=RASLegacy!Xpndr, 7, 243, 305, 57 gauge12=RASLegacy!Autopilot, 5, 177, 292, 62 gauge13=RASLegacy!DME, 4, 305, 256, 46 gauge14=RASLegacy!VM1000C, 579, 0, 445, 446 gauge15=RASLegacy!Annunciator, 0, 379, 453, 68 gauge16=RASLegacy!AOA_Pro, 347, 204, 106, 63 gauge18=RASLegacy!Master_Warn, 346, 271, 108, 107 // =============================================================================== // IMPORTANT - 'gauge19'. 'gauge20, 'gauge22', and 'gauge23' BELOW CAN BE OVERWRITTEN // BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY EDITING THIS FILE // IF YOU WANT TO CHANGE THE GPS ENTRIES AND DON'T WANT THEM OVERWRITTEN IN ANY // CIRCUMSTANCE THEN CHANGE THE GAUGE NUMBERS. EG - CHANGE 'gauge 19' TO 'gauge22' // =============================================================================== //gauge19=fs9gps!RAS_gps_500, 1, 607, 502, 416 gauge20=RASLegacy!Blank, 0, 0, 1, 1 gauge21=Config!AdfDip, 1019, 1023, 1, 1 gauge22=RASLegacy_Sound!Sound, 1,1,2,2,./SimObjects/Airplanes/RealAir Legacy/Panel/Sound/RASLegacy_Sound.ini gauge23=RASLegacy!Sound_Manager, 1,1,3,3 [Default View] X=0 Y=0 SIZE_X=8192 SIZE_Y=3500 [Color] Day=255,255,255 Night=255,255,255 Luminous=201,64,64 BTW it doesn`t matter which plane I try to install the GNS 530 into, the issue is always the same. I´d appreciate any help you could provide. Thanks, Fabian

Thank you, I´ll try that. But if the network adapters were in the wrong order, wouldn´t it affect all the instruments and not only the A2A ones? Because as I said, the standard gauges all work perfectly. Nevertheless, I´ll give it a chance as soon as I have the time.