Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

15 Good

About aua668

  • Rank
    Flight Student - Solo

Recent Profile Visitors

2698 profile views
  1. There is a legacy proxy available, which might help. I have not tested it. But this proxy should provide the datafedd to legacy programs. In the VATGER forum you will find an article about this piece of software. The only problem: It's in German language. https://board.vatsim-germany.org/threads/legacy-status-proxy-data-feed-kompatibilität-für-unmigrierte-passive-clients.66112/ Maybe this fixes the problem. But as I said: I have not tested it, as I use VATSPY for checking VATSIM traffic. Rgds Reinhard
  2. Yes - It's just an USB connection and in fact there is some joystick hardware inside. So it's a normal axis, which you can map to the steering tiller axis via FSUIPC. Rgds Reinhard
  3. Hi, I am using this device for the planes I am flying: http://www.schillermetall.de/tiller.html Very solid piece of work. Rgds Reinhard
  4. Hi, If you are aware, how to program in LUA provided by FSUIPC, you can decrease/increase in steps (-10,-1,+1,+10) the speed value by manipulating LVars: -- Inc/Dec IAS function IncDecIAS (pStep) local lIAS = 0 if ipc.readLvar("L:AB_AP_SPDmode_set") == -1 then -- only if pulled if ipc.readLvar("L:AB_AP_SPDMACH") == 0 then lIAS = math.floor(ipc.readLvar("L:AB_AP_SPEED_Select")) else lIAS = math.floor(ipc.readLvar("L:AB_AP_Mach_Select") * 100 + 0.5) end lIAS = lIAS + pStep if ipc.readLvar("L:AB_AP_SPDMACH") == 0 then if lIAS < 100 then
  5. Operating System: Windows 10 Home OEM 64-bit Simulator version: P3D 5.1 HF1 Airbus version: A320 Professional Experimental Add-ons in use: AviaServer, ActiveSky (on remote PC), vPilot, Orbx products, Aerosoft addon scenery, other scenery vendors, Navigraph actual AIRAC System specs: Intel - Core i7-8700K 3.7GHz 6-Core Processor, Cooler Master - Hyper 412S 52.6 CFM CPU Cooler, Asus - Prime Z370-A ATX LGA1151 Motherboard, Corsair - Dominator Platinum 16GB (2 x 8GB) DDR4-2666 Memory, Samsung - 960 Pro 1TB M.2-2280 Solid State Drive, 2x Asus - GeForce GTX 1080 Ti 11GB POSEIDON
  6. Hi, This (old) problem hit me now rhe second time; During a flight from LOWW to UDYZ suddenly the managed speed (set via CI15 to 0.78) on FL370 was commanding 113 kn. The plane slowed down and was near stall. Luckily I disengaged the autopilot, lowered the nose and could by that recover the flight. From that point in time I could only manually set the speed. Managed speed did not recover to normal operation. There is an older (locked) thread describing the problem. I use the A320 vor P3D 5.1 latest HF in the beta channel. Maybe you can check again, if you are able to de
  7. Hi, Many thanks for your answer. In the meanwhile I tried it out of curiosity on another flight. I changed the arrival procedure during CRZ and I could change Vapp as expected. So I could not reproduce the behavior. When it happened the last time there was no chance to enter any value there - the button was simply not reacting. So I assume, that under certain conditions there is a small bug, which blocks the input. And as you said, it is really seldom, that you correct the value. For the gust estimation - I am not sure, if Aerosoft has implemented that feature you described That's
  8. Hi, My Setup: A320 Professional - P3D v5.1 latest HF. AviaServer for operating the MCDU on a Android tablet. On the PERF page of the MCDU for the approach you can set beside other values the Vapp speed. Normally the proposed value fits quite well but there are cases, where you want to adjust it (gusty wind, etc.). This works fine, as long as you have not activate the approach of course. Then a change of values is not possible anymore, as far as I know. At my last flight I was in cruise and had already entered all the values for approach (QNH, temperature, et
  9. Hi, I use the A320 Pro version with P3D 5.1 (latest Hotfix). I control my radios via GoFlight hardware. I set the standby frequency (COM1 and COM2) with rotaries via the following FSUIPC/P3D controls: 66434 COM_RADIO_FRACT_DEC_CARRY 66435 COM_RADIO_FRACT_INC_CARRY 65636 COM_RADIO_WHOLE_DEC 65637 COM_RADIO_WHOLE_INC and 66439 COM2_RADIO_FRACT_DEC_CARRY 66441 COM2_RADIO_FRACT_INC_CARRY 66436 COM2_RADIO_WHOLE_DEC 66437 COM2_RADIO_WHOLE_INC This works fine in the A320 like for many other aircrafts (stock air
  10. Hi, I am controlling the COM frequencies with some hardware units (GoFlight). Before the update this did work without any problem. And today after the last update suddenly it didn't anymore. Waiting for the fix too... Rgds Reinhard
  11. Hi, Check this thread: https://www.avsim.com/forums/topic/548775-vertx-da62-pfpx-profile/ Rgds Reinhard
  12. Hi, Don't use the buttons appearing on the top but use the button in the left top corner for computing and releasing. Much better that way. Rgds Reinhard
  13. Mathijs, Thanks - works perfectly! One question in that context: Would it be possible in future updates to allow also to map it directly to the tiller axis provided by P3D (instead of throttle 3)? The reason: if you calibrate the axis via FSUIPC, you have an option for setting a slope. This means you can get more precise steering in the middle and more deviation on the extreme sides for example. For a throttle axis this slope setting works different compared to the tiller axis or the rudder axis. FSUIPC only manipulates the curve right of the zero point. If you have FS
  14. Hi, Is the a chance to map the PEDAL DISC on the tiller to a button or is the a LVar available? Rgds Reinhard
  15. Hi, Is it possible to disable these features? Same with the automatic opening of the table at cruise level? An option for turning this off would be nice. Rgds Reinhard
  • Create New...