Jump to content

aua668

Members
  • Posts

    135
  • Joined

  • Last visited

About aua668

Recent Profile Visitors

2782 profile views

aua668's Achievements

Newbie

Newbie (1/14)

  • Reacting Well Rare
  • Week One Done
  • One Month Later
  • One Year In Rare

Recent Badges

15

Reputation

  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 lIAS = 100 end if lIAS >= 399 then lIAS = 399 end else if lIAS < 10 then lIAS = 10 end if lIAS >= 99 then lIAS = 99 end end if ipc.readLvar("L:AB_AP_SPDMACH") == 0 then ipc.writeLvar("L:AB_AP_SPEED_Select", lIAS) else ipc.writeLvar("L:AB_AP_Mach_Select", lIAS / 100) end end end This function can be called via event.button handling. Please understand, that I am not able to provide support, and that you must be aware, what LUA and FSUIPC is about. But it shows you a way, how to handle this. Rgds Reinhard
  5. Operating System: Windows 10 Home OEM 64-bit Simulator version: P3D 5.1 HF1 Airbus version: A320 Professional 1.4.1.2 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 Video Card (2-Way SLI), GoFlight Hardware Description of the issue: This (old) problem hit me now the 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 until final approach. Are you able to reproduce the issue? If so, what are the exact steps you are taking for this issue to happen? No, it's not always happen. I experienced it at 2 flights until now: LOWW-LEBL and LOWW-UDYZ Additional information (route, weights, special area where the issue occurred etc.): I changed inflight the landing runway and approach procedure, as the wind changed on the destination airport. Route: ADAM2C ADAMA Z648 VEDER L140 ALAMU/N0441F350 DCT NARKA/N0439F370 Z650 REBLA M977 ADINA L851 KUGOS UL851 TBN UP146 YAVUZ UB374 INDUR INDU3B Load: 135 pax, 1992 kg cargo, 7356 kg fuel Flight profile on VATSIM: https://vatstats.net/flights/23097918
  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 detect the root cause for that bug. I will use selected speed in the meanwhile, until the bug is fixed. Rgds Reinhard https://forum.aerosoft.com/index.php?/topic/140706-managed-speed-at-cruise/
  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 why I wanted to compensate the predicted gusts at that flight. Thanks for sharing your experience. Rgds Reinhard
  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, etc.). Then I got the information from the ATIS from the VATSIM controller, that the arrival runway has changed. I was still in cruise and changed the arrival procedure in the MCDU. Then I wanted to adopt the Vapp on the PERF page too, as the wind conditions have changed. But after the reprogramming of the arrival route I could no longer change the Vapp speed. It was not possible to enter a new value. Is this by design or is this a bug. I did not yet try to reproduce it yet, but will check this, if I have to change the arrival during flight the next time. Maybe this is a known "feature". Any input from A3xx experts is appreciated. Rgds Reinhard
  9. Hi, I use the A320 Pro version 1.4.1.2 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 aircrafts - but also for the Aerosoft Twin Otter for example). But there is one bug, which only arises in the A320: If I tune the frequency 134.675 and swap this frequency from the standby to the active freuency, this works well. Frequency is tuned and I can communicate with the controller on VATSIM. But as soon as I swap this frequency back to standby, I can't tune it anymore. Something is setting the frequency immediately back to this value, as soon as I try to tune to the next step. And this for increment and decrement (whole and fraction). The only way to get out of this situation is to use the mouse and tune the frequency via the panel. Debugging the FSUIPC log to see the events, I found out, that you are permanently set the COMx standby frequencies to 134.675: 1263688 *** EVENT: Cntrl= 67363 (0x00010723), Param= 136675000 (0x08257eb8) COM1_STBY_RADIO_HZ_SET 1263688 *** EVENT: Cntrl= 67364 (0x00010724), Param= 134675000 (0x0806fa38) COM2_STBY_RADIO_HZ_SET 1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2016 (0x000007e0) PANEL_ID_CLOSE 1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2017 (0x000007e1) PANEL_ID_CLOSE 1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2019 (0x000007e3) PANEL_ID_CLOSE 1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2020 (0x000007e4) PANEL_ID_CLOSE 1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2022 (0x000007e6) PANEL_ID_CLOSE 1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2023 (0x000007e7) PANEL_ID_CLOSE 1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2024 (0x000007e8) PANEL_ID_CLOSE 1263703 *** EVENT: Cntrl= 66508 (0x000103cc), Param= 2025 (0x000007e9) PANEL_ID_CLOSE 1263703 *** EVENT: Cntrl= 66834 (0x00010512), Param= 0 (0x00000000) FREEZE_ALTITUDE_SET 1263703 *** EVENT: Cntrl= 66828 (0x0001050c), Param= 0 (0x00000000) FREEZE_ATTITUDE_SET 1263735 *** EVENT: Cntrl= 66717 (0x0001049d), Param= 1 (0x00000001) TURBINE_IGNITION_SWITCH_TOGGLE 1263735 *** EVENT: Cntrl= 66717 (0x0001049d), Param= 2 (0x00000002) TURBINE_IGNITION_SWITCH_TOGGLE 1263735 *** EVENT: Cntrl= 66466 (0x000103a2), Param= 0 (0x00000000) COM_RECEIVE_ALL_SET 1263735 *** EVENT: Cntrl= 67363 (0x00010723), Param= 136675000 (0x08257eb8) COM1_STBY_RADIO_HZ_SET 1263735 *** EVENT: Cntrl= 67364 (0x00010724), Param= 134675000 (0x0806fa38) COM2_STBY_RADIO_HZ_SET The radios worked fine, until you changed something in one of the previous updates, which broke the radios for many users in this forum completely. The last version in the experimental stream repaired this - but obviously not completely. I know, that this special frequency worked in the past without problems. Why? That's simple. That's the frequency of LOWW_APP, which is the home base of my VA. So I fly typically quite often in and out of Vienna. I always can reproduce this error - but only in the A320 Pro. All other aircrafts (Majestic Q400, Twin Otter, C172, etc.) work perfectly. Maybe some rounding or similar problem, which does not allow to tune to the next step with one of the controls above. Rgds Reinhard
  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 FSUIPC, you can check the difference. Due to the nature of the slope of a throttle axis, this feature cannot be used for the tiller mapped via a throttle axis. But the original problem is solved. Thanks for the quick reaction. I really overlooked that variable in the long list. Rgds Reinhard
  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, It's a long time ago, when I flew a plane with the default autopilot, but as far as I remember, the ALT mode behaves different in the Twin Otter compared to the standard AP. isn't it? The default AP climbs or descends to the selected altitude and you can modify the VS to reach that altitude. The Twin Otter ALT button just holds the current altitude, as soon as you push it. From the P3D manual: 5 - Altitude hold mode selector button The altitude hold mode selector button engages the autopilot's altitude hold mode. When engaged, the aircraft climbs/descends to the altitude set in the altitude selector at the rate set in the vertical speed selector (see below). Rgds Reinhard
×
×
  • Create New...