Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

30 Neutral

About DanW

  • Rank
    Member - 1,000+

Profile Information

  • Gender
  • Location

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

2,013 profile views
  1. Hi Scott, Can you please include a toggle mode for all panel lights in next version? I only use 1 button for lights. Below works for this: function NGX_LIGHT_PANEL_ALL_toggle () local i if ipc.readLvar('ngx_switch_757_a') == 300 then for i = 1, 300 do NGX_LIGHT_PANEL_R_dec () NGX_LIGHT_PANEL_L_dec () NGX_LIGHT_PDST_dec () NGX_LIGHT_OVH_dec () NGX_LIGHT_CB_dec () end NGX_LIGHT_ALL_show () else for i = 1, 300 do NGX_LIGHT_PANEL_R_inc () NGX_LIGHT_PANEL_L_inc () NGX_LIGHT_PDST_inc () NGX_LIGHT_OVH_inc () NGX_LIGHT_CB_inc () end NGX_LIGHT_ALL_show () end end many thanks
  2. Hi, One thing I noticed is the landing gear script doesn't always move the landing gear up, just the handle itself. So I map it to the FSX Default landing gear which works fine. Below are some new scripts if you would like to add to the module? I assign the nose wheel steering to the A/T switch since there's no A/T in Q400. Also a script to toggle all panel lighting happen in one go for a spare button. function NWS_on () ipc.writeLvar("SIDE_PNL_STEERING", 1) DspShow ("NWS", "on") end function NWS_off () ipc.writeLvar("SIDE_PNL_STEERING", 0) DspShow ("NWS", "off") end function PANEL_LIGHT_ALL_TOGGLE () if ipc.readLvar('OHD_PNL_LIGHTS_GLARESHIELD_KNOB_ANGLE') == 0 then OHD_PanelL_All_50() else OHD_PanelL_All_0() end end
  3. It's pretty much only the NAV/ADF navigation radios you can't use with hardware, since they are the only ones that require to be linked into the Q400 systems. If you are only using NAV for ILS - then let the FMS tune it for you. * COM radios - use default FSX radios (COM only not NAV) with the Radio panel or VRInsight MCP combo. You can still hear the audio from the tuned frequency. Just ignore what is in the VC.You can see the frequency on your hardware anyway. * Transponder I haven't tried with VATSIM online, but I think if you keep it linked to default FSX transponder you can keep it that way, and other addons that require your transponder code will see the FSX one. * Transponder/TCAS mode - Map the transponder "MODE" button to a mouse macro that you create by holding the button until it goes to ALT (TCAS). This then becomes a toggle switch you can toggle between standby and ALT/TCAS. Changes to radios in the VC will update what you see in hardware since the VC changes also update FSX, it's just not the other way around i.e. changes in FSX don't update the VC. But this doesn't matter except for radio navigation.
  4. Regarding repaints you need to be backing up your databases and all files from users/user/appdata/flight1/ut2 I think you can add it manually by 1. Adding it to your exe.xml 2. Adding to your simobjects.Cfg 3. Disabling all prepar3d default traffic bgls 4. Copying any other bgls from FSX that ut2 installs. But EMT is better and safer! But be careful any new install will overwrite your data. So backup everything in AppData and ut2 app folder to be sure. I think the power pack can help you backup too
  5. Does FS Global alter terrain.cfg? Or only scenery.cfg?
  6. I actually have both UT2 and P3D set to 0 now. Since I purchased VoxATC it makes enough traffic from the UT2 Aircraft. I haven't upgraded to 2.5 yet, but I hope voxatc can still find the UT2 AI in the new cfg..
  7. Note you don't need any traffic in P3D unless you run extra traffic bgl eg for specific payware airports that install traffic. UT2 injects traffic even if P3D set to 0 percent traffic.
  8. Anyone got this working with Prepar3d version of the 777?
  9. Aerosoft downloads section,lots of stuff
  10. Interesting because transponder mode works for me. He pops up the 2d. I'll have to double check it worked through next flight. V speed callouts work but I set them myself in MCE window. Are you saying it will update automatically?
  11. Hi, A couple of things with the Majestic Q400 not working with latest Majestic patch 1012 and Prepar3d 2.4: 1. After MCE has touched the flaps, the state of the flaps is not recognised by addons anymore: a) I couldn't request MCE to retract them on climb b) RAAS didn't recognise my flaps config and gave warnings c) My VA ACARs system didn't record flaps retraction on takeoff when it usually does without MCE d) MCE refuse to put flaps down in approach flow and refuse to put them up after landing. It's like it couldn't access them anymore. 2. I can command SEATBELTS OFF by voice, various combinations work. However the VoxScript fails to execute this command. I tried various combinations, all using the GUI and the test never executed these. 3. Voice test button doesn't work in the GUI when configuring copilot etc. Not a big deal. Could be related to Win 8.1 64bit. Unfortunately this is all a fresh install so I can't say any particular thing causes these (windows, prepar3d or whatever). I have been flying without MCE prior to this and only just started using it again recently. Other than the above, all Q400 flows and commands I have working well and have built my custom flows it works great. Thanks!
  12. I don't follow their forums, did anyone see any plans to make the 2160 as well?
  13. Very important question! You guessed right, you don't need to setup LINDA, in fact you can't actually use LINDA as it's meant to be used if you use SPAD, because you can't assign SPAD controls to things in LINDA. So you can install LINDA, backup the scripts then remove it. Then in SPAD map things to virtual joystick buttons, making good use of the Profile feature. Then in FSUIPC assign those virtual joystick buttons to LINDA scripts that you have copied, or to FSUIPC mouse macros if available. Make good use of both the Profile feature, and the ShortName feature together and you only have to do setup once for each plane type.
  • Create New...