Lizz

Hi Guys, Just received my second X-plane PC to be used as a master for the visuals. The GPU is a MSI GeForce GTX 970 Gaming 4GB Windows 7 All drivers are installed already but I would like to know what the best driver for this card is at the moment? In april the 347.88 WHQL seemed to be the correct choice...... Any advice??

yep that was it, thanks for reminding......

ahhhh that's a good one Reinhard, I don't think so.... I will check it asap...

I need some advice: I just installed a second X-Plane PC into my Simulator, this PC will be the Master while my 'old' will become the Slave for the visuals. My panelbuilder software runs on a third PC, nothing changed here. I transferred all plugins including Panelbuilder receiver and sender to the X-plane installation on the new Master PC. It connects but all gauges have gone bezerk..... no valid indications whatsoever. My question: What do I need to do to correct this, did I forgot something or do I need to simply re-install Panelbuilder on the New Master PC? Or is it a setting somewhere on the new Master PC (I did disable the Win7 firewall) Any advice?

What happened to my sim...???? Well....I just upgraded my TEST version of X-plane to 10.40b3 (I always keep two versions, one that runs stable in my Sim and another one for testing purposes). I was so exited about your posting here that I had to see it myself, and I must admit it is quite a change, woooow. I made a testflight around KSEA and framerates are better (more solid around the 30's), seems that the landscape looks better and those default airports included in this release are great too more houses etc. I didn't chage any setting compare with version 10.36, only updated. I didn't use SkyMaxx yet, will be the next step to install it into this test version as well. Seems also that framerates at night are much higher.... I saw the occasional stutter though, but maybe I have to switch ON extended dsf's....... Need to do much more testing but this really looks promising I must say. Will report back when I installed and tested SkyMaxx pro.

Hi Sesquashtoo Well, that's a very enthousiastic advertisement for X-Plane, I like it very much. Being an X-plane 'Die Hard" myself I'm very interesed to know your system configuration. I just ordered myself a new PC which will become the Master PC in a '2 PC visuals through 2 beamers' configuration. Can you tell some more about your config and settings?

Everything went OK, software is upgraded to the latest version. Great to have the Roll Trim available now! One issue I would like to bring up, it's an old issue and not related to this upgrade, it was present before! I use the EFIS Fuel Remaining display and when I switch Off the Avionics most of the EFIS instruments disappear (as it should) but this one stays PARTLY on the display. (don't know how to attach pictures.......) Can I do something about it or is it a 'bug'? regards. Lisette

Hi Reinhard, Thank you very much for the quick reply, just added 'start' and it works great, exactly what I was looking for. Also good to hear that I do not need to register again, so I will start updating my version. Thanks again for your support.

I have two questions about panel builder. I use EFIS panel builder to show the Engine instruments for various turboprop aircraft in my home build simulator. Questions: 1. I want to upgrade to the newest version as it offers automatic panel switching, which I think is a great feature.... As I have a somewhat older version I need to remove the current install and install the new version and then register again. How to ensure that the current panels I configured are saved and available after the upgrade in exactly the same configuration? 2. As I'm in a simulator, preferably I don't want to start applications by clicking with the mouse. So I put the panel builder in my PC startup folder to start it automatically which works fine. But from there I still need to start the panel itself to be displayed on the screens in the cockpit. Is there a way to launch the panel upon startup or is this arranged by the new panel switching feature? Thanks for your support. Regards, Lisette

I just connected a second Phidget LED64 board to drive my annunciator panel in my homecockpit. It works fine and I was very pleased. So I started to make the final assignements for all datarefs to be adressed by the Phidget boards and adapted the existing config file accordingly. When I started X-plane it simply crashed and looking into the log.txt file it crashed because of the Phidget64 sender application. Putting back the original configfile (also with 2 boards) doesn't crash X-plane so I started to look for the differences between the two files. Unfortunately I am unable to determine what makes x-plane crash on one file while it simple starts OK on the other file. Below you will find both config files (the one that crashes X-plane and the one which is OK). Problem is that the Phidget64 plugin simply doesn't give any clue on what is causing the crash, it simply crashes X-plane and that's it!!! Or is there a 'hidden' logfile somewhere that gives some insight on why the plugin crashes? The manual is also not very clear on any required conventions (e.g. remarks in the file, sequence, valid Datarefs etc...) other then the structure of one line entry. I'm very happy that it is possible to connect 2 Phidgetboards and it works great but this kind of behaviour drives me totally nuts..... :wacko: :wacko: This is the configfile that crashes X-plane: ;Copyright © 2013, BajuSoftware LLC ;Configuration File for datarefs ;Version 2.41 ;Format: Port|ID|dataref ;------------------------------------------ ;IP Address 127.0.0.1 ;Interval 0.2 ;DataRefs 50001|1I_00@0|sim/cockpit2/annunciators/flight_director 50001|1I_01@0|sim/cockpit2/annunciators/autopilot 50001|1I_02@0|sim/cockpit2/annunciators/master_warning 50001|1I_03@0|sim/cockpit2/annunciators/master_caution 50001|2I_04@0|sim/cockpit2/annunciators/generator_off 50001|2I_06@0|sim/cockpit2/annunciators/igniter_on 50001|2I_08@0|sim/cockpit2/annunciators/oil_pressure_low 50001|1I_10@0|sim/cockpit2/annunciators/ice 50001|1I_11@0|sim/cockpit/warnings/annunciators/ice 50001|1I_12@0|sim/cockpit2/annunciators/pitot_heat 50001|1I_13@0|sim/cockpit2/annunciators/landing_taxi_lite 50001|1I_14@0|sim/cockpit2/annunciators/fuel_quantity 50001|1I_15@0|sim/cockpit2/annunciators/inverter_off 50001|1I_16@0|sim/cockpit2/radios/indicators/outer_marker_lit 50001|1I_17@0|sim/cockpit2/radios/indicators/middle_marker_lit 50001|1I_18@0|sim/cockpit2/radios/indicators/inner_marker_lit 50001|1I_19@0|sim/cockpit2/annunciators/autopilot_disconnect 50001|2I_20@0|sim/cockpit2/annunciators/fuel_pressure_low 50001|2I_22@0|sim/cockpit2/annunciators/oil_temperature_high 50001|3F_24@0|sim/flightmodel2/gear/deploy_ratio 50001|3F_27@0|sim/flightmodel2/gear/deploy_ratio ; 50001|1I-03@1|sim/cockpit2/annunciators/hvac 50001|1I-07@1|sim/cockpit2/annunciators/cabin_door_open 50001|1I-10@1|sim/cockpit2/annunciators/landing_taxi_lite 50001|1I-12@1|sim/cockpit2/annunciators/GPWS 50001|2I-13@1|sim/cockpit2/annunciators/fuel_pressure_low 50001|2I_18@1|sim/cockpit2/annunciators/generator_off 50001|2I-20@1|sim/cockpit2/annunciators/oil_pressure_low 50001|2I_22@1|sim/cockpit2/annunciators/engine_fire 50001|2I_24@1|sim/cockpit2/annunciators/bleed_air_off 50001|1I-26@1|sim/cockpit2/annunciators/fuel_quantity 50001|1I-27@1|sim/cockpit2/annunciators/hydraulic_pressure 50001|2I_28@1|sim/cockpit/warnings/annunciators/chip_detected 50001|1I-30@1|sim/cockpit2/annunciators/ice 50001|1I_31@1|sim/cockpit2/annunciators/pitot_heat 50001|1I_33@1|sim/cockpit2/annunciators/autopilot 50001|1I-34@1|sim/cockpit2/annunciators/low_voltage 50001|1I-35@1|sim/cockpit2/annunciators/no_inverters 50001|1I-36@1|sim/cockpit2/annunciators/cabin_altitude_12500 50001|1I-37@1|sim/cockpit/warnings/annunciators/autopilot_disconnect 50001|1I-48@1|sim/cockpit2/annunciators/crossfeed_on 50001|1I_50@1|sim/cockpit2/annunciators/yaw_damper 50001|1I-51@1|sim/cockpit2/ice/ice_window_heat_on 50001|1I-54@1|sim/cockpit2/ice/ice_inlet_heat_on 50001|1I_56@1|sim/cockpit/electrical/landing_lights_on 50001|1I-57@1|sim/cockpit2/ice/ice_surface_boot_on 50001|1I_59@1|sim/cockpit/electrical/taxi_light_on 50001|1I-60@1|sim/cockpit2/ice/ice_prop_heat_on 50001|1I_62@1|sim/cockpit2/annunciators/flight_director 50001|1I-63@1|sim/cockpit2/annunciators/speedbrake This is the configfile that works OK: ;Copyright © 2013, BajuSoftware LLC ;Configuration File for datarefs ;Version 2.41 ;Format: Port|ID|dataref ;------------------------------------------ ;IP Address 127.0.0.1 ;Interval 0.2 ;DataRefs 50001|1I_00@0|sim/cockpit2/annunciators/flight_director 50001|1I_01@0|sim/cockpit2/annunciators/autopilot 50001|1I_02@0|sim/cockpit2/annunciators/master_warning 50001|1I_03@0|sim/cockpit2/annunciators/master_caution 50001|2I_04@0|sim/cockpit2/annunciators/generator_off 50001|2I_06@0|sim/cockpit2/annunciators/igniter_on 50001|2I_08@0|sim/cockpit2/annunciators/oil_pressure_low 50001|1I_10@0|sim/cockpit2/annunciators/ice 50001|1I_11@0|sim/cockpit/warnings/annunciators/ice 50001|1I_12@0|sim/cockpit2/annunciators/pitot_heat 50001|1I_13@0|sim/cockpit2/annunciators/landing_taxi_lite 50001|1I_14@0|sim/cockpit2/annunciators/fuel_quantity 50001|1I_15@0|sim/cockpit2/annunciators/inverter_off 50001|1I_16@0|sim/cockpit2/radios/indicators/outer_marker_lit 50001|1I_17@0|sim/cockpit2/radios/indicators/middle_marker_lit 50001|1I_18@0|sim/cockpit2/radios/indicators/inner_marker_lit 50001|1I_19@0|sim/cockpit2/annunciators/autopilot_disconnect 50001|2I_20@0|sim/cockpit2/annunciators/fuel_pressure_low 50001|2I_22@0|sim/cockpit2/annunciators/oil_temperature_high 50001|3F_24@0|sim/flightmodel2/gear/deploy_ratio 50001|3F_27@0|sim/flightmodel2/gear/deploy_ratio ; 50001|1I_00@1|sim/cockpit2/annunciators/master_warning 50001|1I_01@1|sim/cockpit2/annunciators/stall_warning 50001|1I_02@1|sim/cockpit2/annunciators/yaw_damper 50001|1I_03@1|sim/cockpit2/annunciators/pitot_heat 50001|1I-28@1|sim/cockpit2/annunciators/cabin_altitude_12500 50001|1I-05@1|sim/cockpit/warnings/annunciators/autopilot_disconnect 50001|1I-06@1|sim/cockpit/warnings/annunciators/autopilot_trim_down 50001|1I-07@1|sim/cockpit/warnings/annunciators/autopilot_trim_up 50001|1I-08@1|sim/cockpit2/annunciators/landing_taxi_lite 50001|1I-09@1|sim/cockpit2/annunciators/cabin_door_open 50001|2I-10@1|sim/cockpit2/annunciators/auto_feather_arm 50001|1I-12@1|sim/cockpit2/annunciators/low_voltage 50001|1I-14@1|sim/cockpit2/annunciators/hydraulic_pressure 50001|1I-15@1|sim/cockpit2/annunciators/speedbrake 50001|1I-16@1|sim/cockpit2/annunciators/GPWS 50001|1I-17@1|sim/cockpit2/annunciators/ice 50001|2I-18@1|sim/cockpit2/annunciators/fuel_pressure_low 50001|2I-20@1|sim/cockpit2/annunciators/oil_pressure_low 50001|1I-22@1|sim/cockpit2/annunciators/fuel_quantity 50001|2I-23@1|sim/cockpit/engine/fuel_pump_on 50001|1I-29@1|sim/cockpit2/annunciators/no_inverters 50001|1I_33@1|sim/cockpit/electrical/taxi_light_on 50001|1I-48@1|sim/cockpit2/ice/ice_window_heat_on 50001|1I-49@1|sim/cockpit2/ice/ice_surface_boot_on 50001|1I_50@1|sim/cockpit2/annunciators/flight_director 50001|1I-51@1|sim/cockpit2/annunciators/hvac 50001|1I-52@1|sim/cockpit2/ice/ice_prop_heat_on 50001|1I_53@1|sim/cockpit/electrical/landing_lights_on 50001|2I-54@1|sim/cockpit2/annunciators/generator_off 50001|2I-58@1|sim/cockpit2/annunciators/igniter_on 50001|1I-60@1|sim/cockpit2/annunciators/crossfeed_on 50001|2I-61@1|sim/cockpit2/annunciators/bleed_air_off 50001|1I-63@1|sim/cockpit2/ice/ice_inlet_heat_on

Hi, I would like to add more specific datarefs to the EFIS panelbuilder sw specifically for annunciators. e.g. I want to add a Bleed Air fail annunciator so I edit the Engine section in the PanelBuilderSender.cfg file as follows: ;Annunciator - Engine 44001|4I_FIRE|sim/cockpit2/annunciators/engine_fires 44001|4I_CHIP|sim/cockpit2/annunciators/chip_detected 44001|4I_OTMP|sim/cockpit2/annunciators/oil_temperature_high 44001|4I_GENR|sim/cockpit2/annunciators/generator_off 44001|4I_FPRE|sim/cockpit2/annunciators/fuel_pressure_low 44001|4I_OPRE|sim/cockpit2/annunciators/oil_pressure_low 44001|4I_REVR|sim/cockpit2/annunciators/reverser_deployed 44001|4I_AIGN|sim/cockpit2/annunciators/igniter_on 44001|4F_COWL|sim/cockpit2/engine/actuators/cowl_flap_ratio 44001|4F_CHOT|sim/cockpit2/engine/actuators/carb_heat_ratio 44001|4I_FPMP|sim/cockpit2/engine/actuators/fuel_pump_on 44001|4I_EICE|sim/cockpit2/annunciators/ice_vane_extend 44001|4I_FTHR|sim/cockpit2/annunciators/auto_feather_arm 44001|4I_BLDF|sim/cockpit/warnings/annunciators/bleed_air_fail There was no explanation in the manual of the entry in this config file so I just tried the above. I hoped that the dataref would show up in the selection window (see below) but it didn't. How can I add a dataref to the programs configuration?

Nooo not at all, I think it's great, thanks!!!!! Partytime...

Did I won....??? :rolleyes:

Santorini....in greece

I dont't know if this is the 'common' behaviour in X-plane but I do know that in the real world no pilot would enter such a huge red area displayed on the weather radar. They will request for a route around it. I'm often flying while listening to realATC through the internet and when I'm seeing those kind of Red areas on the map I hear the real world pilots constantly requesting for vectors around it. :rolleyes: It seems that you crashed your aircraft by entering this severe weather.......

Only 10 female simmers overhere..... Oh, I like Sushi very much!

Sal, Just checked my settings in the LED64 client. In the IP adress field there is the IP adress of the LAN connection of the PC that runs X-plane and the client (same PC), 192.169.1.100. I don't know if I entered this or that the client detected it automatically. It look like it's done automatically as the field is uneditable. the portnumber is 8888, but this can be anything as far as I know as long as they are the same in the plugin and the client. There are no further settings done X-plane. The manual states that the UDP port that is used has nothing to do with the UDP settings in X-plane. Maybe you could just try another portnumber? Could you let me know how the Phidgetservo works once you get it operational? Maybe I'm going to use it for a few instruments in my cockpit. Hope this helps. Lizz

Hi Sal, I'm not having any experience with the servo plugin from Simplugins but I am using the Led64 phidget cards with their led64 plugin. This works great with X-plane, I use it to control all annunciators in my homecockpit. I had some trouble to get it working correctly but Reinhart from Simplugins is extremely cooperative to help. He adapted his plugin to work with floatingpoint datarefs and now I'm evaluating a new version that should be capable to control two Phidget Led cards which gives 128 leds to control. I would advise you to just send an e- mail to their support adress and he will come back to you. Btw the UDP port setting need to be the same in the client as well as the plugin, you need to enter those numbers in the client as well as the .ini file. This is identical as with the LED64 plugin. Regards, lizz

Hi Rob, Just installed your two static aircraft files and made two legs, LSZH-LSZA and back. I must say your work is exellent, I think you even might have saved Aerosoft's Zurich scenery. At least I decided not to buy Zurich because of it's emptyness until i came across your files through the x-plane blog. I purchased it and with your files the airport is abolutely briljant! Aerosoft did a fantastic job modelling the airport. One remark though for Lugano; there are a few Saabs in the way when taxiing to the parking..... Are you planning to do this for schiphol amsterdam as well? Thanks again for your great work. Regards, Lizz