Jump to content

aua668

members
  • Content Count

    114
  • Joined

  • Last visited

About aua668

  • Rank
    Flight Student - Solo

Recent Profile Visitors

2394 profile views
  1. Hi, Try: [HKEY_CURRENT_USER\Software\FlightSimSoft.com\PFPX] and there the "DataFolder" entry. Rgds Reinhard
  2. Hi, If you search the registry for PFPX you will find a registry value containing the data path. You can change this and copy your PFPX data directory to that new location. I have done this and moved my directory to my NAS, so that the data could be saved with my regular backup of my NAS. But as written this is not a supported option, as normally you are not able to change this from UI. So you can do this on your own risk. I never had a problem.Maybe this could get an officially supported option in one of the next releases. Would be nice. Rgds Reinhard
  3. Hi, Check the FSUIPC Lua Library document for the event functionality. In the FSUIPC Lua Plug-Ins zip file you fin a lot of samples, which could help you to develop code. If you are not firm with programming, you also could search for LINDA, which provides a lot of routines for accessing the A3xx functionality. I include here a reduced sample of a LUA code for my GoFlight hardware, which toggles LOC and APPR. You only have to add this LUA to the [Auto] section of your FSUIPC INI file, so that it is executed at startup. Of course you have to add the correct values for joystick and button number. The event function guarantees, that the routine is waiting for the defined button presses to trigger the referenced function. -- A320_GF_Sample.lua -- define joystick variables - depends on your system local GF_Joystick = 157 -- GoFlight joystick number local GF_JoyButton_VORLOC = 7 -- GoFlight button number VOR/LOC local GF_JoyButton_APPR = 19 -- GoFlight button number APPR -- toggle LOC function LOCToggle (joynum, button, downup) -- toggle LOC ipc.writeLvar("L:AB_AP_LOC", 1 - ipc.readLvar("L:AB_AP_LOC") ) ipc.writeLvar("L:SmallOverheadPushButtons", 1) end -- toggle APPR function APPRToggle (joynum, button, downup) -- toggle APPR ipc.writeLvar("L:AB_AP_LOC2", 1 - ipc.readLvar("L:AB_AP_LOC2") ) ipc.writeLvar("L:SmallOverheadPushButtons", 1) end -- LOC trigger event.button(GF_Joystick, GF_JoyButton_VORLOC, 1, "LOCToggle") -- APPR trigger event.button(GF_Joystick, GF_JoyButton_APPR, 1, "APPRToggle") Further discussion should be done in the FSUIPC forum, which would be the right place to get additional information. Rgds Reinhard
  4. Hi, You have a typo in your LVars: L:AB_AP_LOC would be the correct LVar. You missed an "A" during copy/paste obviously. Btw.: I also see, that you don't use event-driven code in LUA. You should study the manual for the concept of events. This is much more effective instead of always loading the LUA code each time you press a button. Rgds Reinhard
  5. Hi, MSN = Manufacturer's Serial Number. At the moment you only can enter something like this in the aircraft configuration file: <MSN>065</MSN> If you add such a line it will be shown in the list. But at the moment there is no field in the UI. Rgds Reinhard
  6. Ohhh - thanks. That explains this behaviour. I planned the flight for the CPT at LGTS today. Many thanks for clarifying this mystery. Topic can be closed. Reinhard
  7. Hi, When I calculate takeoff performance for my OFP PFPX always uses 330/20 as the wind of the departure airport. For the landing performance it is ok. As I am able to manually override the value with the correct wind before calculating, I have a workaround. But it would be nice to fix this with the next version. Rgds Reinhard FLIGHT: (FPL-AUA71TQ-IS -A320/M-SDE2FGIJ1RWY/HB1 -LOWW1800 -N0446F370 ARSIN DCT BABIT DCT VAGEN DCT RAXAD DCT ERANA UT389 ALIKO -LGTS0124 LGKV LWSK -PBN/B1D1S1S2T1T2 DOF/190105 REG/OELBL EET/LHCC0006 LYBA0024 LWSS0056 LGGG0105 SEL/CRGL OPR/AUA ORGN/LOWWAUAO -E/0252) METAR for LOWW (departure) and LGTS (arrival): LOWW 042120Z 29017KT 7000 -SN SCT009 BKN024 00/M02 Q1024 R88/29//95 TEMPO 4000 -SN BR BKN010 LOWW 042015Z 0421/0603 29018KT 9999 -SN FEW010 BKN030 TX04/0523Z TN01/0421Z TEMPO 0421/0506 29020G30KT PROB40 TEMPO 0503/0507 1500 SN BKN012 BECMG 0507/0509 29020G30KT -RA TEMPO 0509/0515 29025G40KT 3000 RA FEW008 BKN012 FM051600 32014KT 9999 SCT030 BKN040 TEMPO 0516/0603 33020G30KT 9999 SHRA FEW010 BKN020 LGTS 042120Z 33015G25KT 0500 R16/0500 R34/0500 +SN BKN004 OVC020 M00/M01 Q1020 R16/555095 NOSIG AMD LGTS 041940Z 0419/0518 34020KT 5000 SN ???005 BKN020 TEMPO 0419/0506 1000 SN BKN004 OVC018 TEMPO 0419/0509 34020G30KT BECMG 0506/0508 7000 SCT006 BKN020 PROB40 TEMPO 0506/0512 4000 SN BKN006 OVC020 TO/Landing Performance in OFP: -------------------------------------------------------------------------------- ** TAKE-OFF DATA LOWW 29 ** COND: 77000 KG // RWY WET // +0C Q1024 330/20 // LMT: STRUCT CONFIG: CONF 1+F // NORM T/O // A/I ENGINE // A/C ON SPEEDS: V1=137 VR=160 V2=161 ENG OUT: CLIMB STRAIGHT AHEAD TO 2100FT. TURN LEFT TO SNU (D115.50) CLIMBING TO 5000FT AND HOLD (350/R). -------------------------------------------------------------------------------- ** LANDING DATA LGTS 34 ** COND: 64500 KG // RWY WET // +0C Q1020 330/15 // LMT: STRUCT CONFIG: CONF FULL // A/I ENG+WING // A/C PACKS ON SPEEDS: VREF=147 VAPP=152 ENG OUT: AT 'THS' 345.0 ENTER HLDG (350 INBD,LT) --------------------------------------------------------------------------------
  8. Hi, As I also had problems with RealLight (multiple graphic cards and P3D 4.4 lead to CTDs), I tried the hint of dandan87 and removed the DLLs. Then I ran the supplied installers for RealLight and TrueGlass again and got the new versions of the DLLs (date 12/25/2018). With these DLLs I am able to start and stop the bus without CTD. But as soon as I am turning on the OVHD integral light, the light goes on shortly and then with a CTD the sim stops again. So the new version is a little bit better but the (known problem) with two graphic cards and RealLight in P3D is still not fixed finally. SoRealLight is still enabled in my bus. Rgds Reinhard
  9. Hi, Your company is licensing a product, which is known to make your product unusable in a certain configuration, which is common in the flightsim world. So you should be interested, to get this solved. While you are not able to solve it technically, you could use your market position to help LM and TFDi to get this solved. That's what I asked you for. BR Reinhard
  10. Hi, I am using the A320 Professional (latest update) under P3D 4.4 / WIN10 in a multi-monitor setup. One curved 32:9 screen for the outside view and two touch screens below for the panel views. I use two Geforce 1080 Ti driving this setup. P3D 4.4. in combination with RealLight has a problem, if you create a second window, undock it and move it to another monitor. As soon as you turn on the integral lights this leads to a CTD. After long experiments sorting out all possibilities I can clearly and reproducable demonstrate, that this the source of my problem. There are several hints in the RealLight forum, that there might be a problem with multiple graphic cards. But no fix so far is available. So at the moment I can only disable RealLight, which makes flying in the night a little bit problematic. Maybe you can work together with LM and TFDi Design to get this solved, as you sell a product by using third party software, which doesn't work in a common setup for flightsim (multi-monitor). Rgds Reinhard
  11. Hi, I have a similar problem with the A3xx professional in P3D v4.3. I have a 32:9 monitor for my outside view and two touchscreens below for the VC panel view. For all my aircraft I have setup a scenario file, where I have two views with user defined cameras. One for outside and one for spanning across the two touchscreens. This works fine for all stock aircrafts, for the Twin Otter and some others. They load correctly.I use two nVidia cards for driving these three monitors. When I start P3D, it loads the scenery, the aircraft and the views correctly. After 10-20 seconds showing the panel and the outside view obviously some initial scripting starts (I assume you initialize the plane and the views etc.) and suddenly P3D crashes to the desktop. Most of the time without any log in the vent viewer. Sometimes you find a reference to some nVidia driver. I use the actual driver version. I changed my scenario and removed the outside view and let P3D start only on one single monitor. Then everything starts fine. I am also able later to create a new view, move it to the 32:9 screen etc. With P3D v3 and the "old" A3xx loading of such a scenario worked fine in the past - no problem. At the moment I cannot automate my startup - I always have to setup views and cameras manually for this plane - very annoying. Rgds Reinhard
  12. Hi, If you know how to write Lvars (e.g. via FSUIPC, LUA or macro etc.) then you could write to the Lvar "L:Windowwiper_Mode" -1=Park, 0=Off, 1=On Rgds Reinhard
  13. Hi, That's definitely not correct. Enclosed find a sample, how we at our VA would calculate your route. And with these values we always get the figures quite correct. You can see, that the pax weight matches quite closely to the value in the Q400 control panel. The small difference at pax weight arises obviously from the rounding between lbs and kg. I have defined the baggage weight as 0 kg in the settings and I enter the figure manually as we get random values from the VA when booking the flight. And the fuel consumption with the profile from the download section in that forum is pretty close to the actual consumption. Rgds Reinhard
  14. I went back to 1.28.9c and the problem is gone. It runs as stable as before. Rgds Reinhard
  15. Hi, Same here. The problem seems to be related to the map display window during the planning process. Tried the several vcredist variants. But it is not stable. Sometimes it works and sometimes it hangs. This was introduced for me with the latest hotfix. Rgds Reinhard
×
×
  • Create New...