Jump to content

Steku

Members
  • Content Count

    292
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

155 Excellent

About Steku

  • Rank
    Member

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The plan was validated before the flight, the screen from P2ATC above is for illustration only, screenshot taken just for this point. Why P2ATC asked me to be AT certain FL over ROPOX if there is no restriction for ROPOX in the STAR?
  2. In some payware planes, like Aerosoft CRJ, there are complex radio systems modelled, which not update the offset P2ATC uses to determine if COM1 or COM2 is set for transmitting/receiving. Would be great to have the option in P2ATC to assign two buttons: one for COM1 and another for COM2 transmitting/receiving, independently from the sim. This would be especially useful for people with extensive hardware panels, who fly mostly without using the mouse.
  3. E-mail sent. Thank you for sorting this out.
  4. The Knobster bridge avialable here: https://axisandohs.weebly.com/downloads.html is described as "knobstertolorbyaaobridge_v1_00_b07.zip". However when the module is downloaded and ran, it displays V1.00 b06 (c)2021 LORBY - SI. Is this just wrong description of the v.b07 or wrong module is posted on the page? I was a happy user of AAO v. 2.24b03 and Knobster bridge 1.00 b06 (version updated for forcing KeyUp event). Yesterday I updated AAO to v. 2.26 b04. In the result my Knobster bridge no longer works 😞 The bridge regonizes the Knobster connected, but the "LED" doesn't turn green when the Knobster is rotated or pushed. Unfortunately I don't have a copy of AAO v. 2.24b03 installer co I can't just reinstall this version. However, I managed to restore my installation of AAO v. 2.24b03 from backup copy (C:\Program Files\LorbyAxisAndOhs_MSFS folder). And it works. Something is probably wrong between AAO v. 2.26 b04 and Knobster Bridge? Possibly AAO v. 2.26 b04 requires the bridge v. v1_00_b07 but this version is not updated on the donwload page. Konbster is a vital component in my setup, so currently seems I'm locked at AAO v. 2.24b03,
  5. Recently I've been flying ROPO 1B STAR in Aerosoft CRJ: I was requested by ATC to pass ROPOX at FL160, while CRJ descent profile predicted much higher altitude at this point (FL305) Why ATC is asking me to pass at fixed FL and not "at or above"? There is no altitude restriction at this point (ROPOX). This happens for most of my approaches in the CRJ. My plans are imported to P2ATC from Navigraph (based on Simbrief) and to CRJ FMS from Simbrief. How should I overcome this, to avoid steep descent, not in line with the descent profile optimal for the CRJ? Should I play with the Descent Rate in P2ATC? To have the FL305 at ROPOX I would need to set crazy Descent Rate in P2ATC (ca. 5000 FPM). I fly in VR, so I setup my plan in P2ATC, file it and from this point on I'm 100% in VR, interacting with P2ATC by voice only. So I would rather avoid manually editing in P2ATC the planned altitude at ROPOX based on the FL provided by the CRJ FMS.
  6. Consider running P2ATC on another, networked PC wide WideFS. P2ATC supports such config.
  7. The problem is that I'm flying in VR, unable to see P2ATC interface, I must rely on voice only. I will try to use copilot option to set my frequencies, to reduce me workload
  8. I'm using Navigraph charts and I always have most current Navigraph DB updated in the P2ATC. I fly in VR, so I use 100% voice communication with P2ATC, I can't see P2ATC interface, so I can't check the freq. in P2ATC. Like in the real world flying, where we have just the controllers voice in the headset and notinh like P2ATC interface. On take-off, while still on TWR freq, I would like to have DEP or APP freq preselected following the relevant Navigraph STAR chart. However P2ATC TWR very often hands me over to different DEP or APP freq than the one specified on the Navigraph chart. At this stage of flight it's difficult to handle the plane and to turn the freq knobs. Quite often P2ATC uses also different GND or TWR freq vs. the ones specified on the charts. Is there a way to convince P2ATC to use the same freq as provided on the Navigraph charts? Or to print a frequency briefing listing all the freq expected during the flight, following the flight plan specified in P2ATC?
  9. It would be great to be able to talk to P2TAC ground controllers to engage pushback start/stop/left/right in MFS2020. I fly in VR, using P2ATC to communicate with ATC verbally (P2ATC app stays in the backgorund). Invoking MFS2020 ATC control window is an immersion killer in VR. Question to the the users: Any ideas to control pushback in VR without invoking MFS2020 ATC window?
  10. Tis issue was related to interim beta version, see here:
  11. With Reverb G2 (Windows Mixed Reality) you can bring the entire desktop to VR, but the way of handling this is not perfect. But it works.
  12. There is a powerful tool allowing assigning buttons/knobs/axes to joysticks, MIDI devices (e.g. Behringer x-Touch Mini), Knobster and even voice commands. For those of you who need more voices in P2ATC it allows converting WinRT voices (not accessible to P2ATC) to SAPI voices (accesible to P2ATC) by automating the required registry editing. It's quite useful, as sometimes Windows update removes the registry edits, forcing you to do the editing again. Axis and Ohs automates this. It's not free but wery powerful, check it out: https://axisandohs.weebly.com/ This tool is especialy useful for cockpit/panel builders, kind of FSUIPC on steroids. There is plenty of information in this forum and on the web regarding WinRt vs. SAPI, so I will no elaboare here, as I'm not an expert in theis area, I just happened to make the registry editing for my needs.
  13. Now I installed 2.6.2.4_x64_beta2a over 2.6.2.3x64_R2 and it doesn't work. Seems like an issue with the beta. Back to 2.6.2.3x64_R2 - it works. Wow! I can control my COM1/COM2 radios using my H/W panel in VR again! And the issue with just "COM" (instead of "COM1" or "COM2") just after connecting to sim - also gone (this is the immediate indicator of the issue, no neet to play with the transmit konb).
×
×
  • Create New...