Jump to content

Sign in to follow this  
duckbilled

After Chaseplane - keyboard, gamepad, GSX and ProATCx issue

Recommended Posts

Posted (edited)

Hi,

I purchased Chaseplane a few days ago, and have not been able to start a flight since then. Not sure if the problem is with Chaseplane, but I haven't had this issue until now. Here is what I have running with each flight. Problem is near the end. Some info first.

I am running:

  • P3D 4.5HF2
  • GSXv2
  • ProATCx
  • Active Sky
  • Environment Force

I am an old user of EzDok so I'm using the same setup that was way back then (seems to work well at first glance). I never installed EZDok on this system. I have been using the default camera system until now. I have stripped the vast majority of my commands out of P3D, and I use FSUIPC5 for controls. I have a Logitech G13 game pad where I have keyboard shortcuts mapped to the keys and then assigned to views in Chaseplane. I also have G13 keys mapped to the shortcuts for opening the GSX menu and the ProATCx menu.

Problem:

After starting a flight, I use GSX to position me at a gate and connect the jetway. Then I move over to ProATCx to get clearance. While I am entering everything into he FMC, I have flightplan info open in the ProATCx menu. Once I am done with this task I switch from windowed to full screen, because I don't need the ProATCx GUI anymore. Shortly after doing this, I lose almost all of my ability to use the keyboard shortcuts for GSX and ProATCx - CP views work for a minute, but those go away as well. In addition, most of the keyboard shortcuts or buttons on my keyboard won't work either. For example, I can use ctrl+alt+del to pull up task manager but I can't use the windows key to bring up the P3D menu or use esc to exit P3D. I also can't manually execute the keybord shortcuts or any other function I have mapped to the keyboard. Because of this, every flight is dead in the water before I even push back. 

I don't see any relevant posts in the ORBX Chaseplane forums, and it really doesn't look like that forum gets a lot of traffic anyway. Any ideas where to start to troubleshoot this?

Thanks!

 

Edited by duckbilled

Windows 10 Pro; P3DV4, ASP4, REXSF, AIGAIM, ProATCx, GSX 

I9-9900k @ 5.0; Asus Maximus XI Hero; Asus Strix GTX 1080ti; 32GB G.Skill Ripjaw DDR4 3600; 2X Samsung 1TB 970EVO; NZXT Kraken X63; Seasonic Prime PX-1000, Single 32" 4k Monitor 



 

Share this post


Link to post

Bump.

In short, installing Chaseplane seems to have disabled my keyboards, sort of.


Windows 10 Pro; P3DV4, ASP4, REXSF, AIGAIM, ProATCx, GSX 

I9-9900k @ 5.0; Asus Maximus XI Hero; Asus Strix GTX 1080ti; 32GB G.Skill Ripjaw DDR4 3600; 2X Samsung 1TB 970EVO; NZXT Kraken X63; Seasonic Prime PX-1000, Single 32" 4k Monitor 



 

Share this post


Link to post

I think It's supposed to run this way. You have to use chaseplane's keyboard inputs that are setup in preferences in Chaseplane. I think you also have to re-set up your joystick buttons and hat in P3D as well. It's confusing but once you figure it out it works fine. Setting up views on your number pad is confusing also, but there's a nice YouTube video somewhere that shows you how it all works.

Share this post


Link to post
11 hours ago, mikegrr said:

I think It's supposed to run this way. You have to use chaseplane's keyboard inputs that are setup in preferences in Chaseplane. I think you also have to re-set up your joystick buttons and hat in P3D as well. It's confusing but once you figure it out it works fine. Setting up views on your number pad is confusing also, but there's a nice YouTube video somewhere that shows you how it all works.

Thanks Milke. The issue I am having is a bit more extensive. Almost every keyboard command is being disabled on all of my keyboards after switching from windowed to full screen. This includes my Windows key, my ESC key, and every keyboard function except ctrl+alt+del.

Also, the G13 isn't necessarily a number pad. You can map keyboard shortcuts to the keys, so the idea works well with Chaseplane and EZdok. The views actually do work with this setup, but they stop working after a period of time.

I just realized that there is an active Chaseplane support forum at AVSIM, so if the mods want to move this over there, feel free. In the meantime, I'm going to keep investigating. It is quite possible that it has noting to do with Chaseplane. I also need to get a handle on when this issue is happening and what actions/settings lead to my keyboards crashing.

 


Windows 10 Pro; P3DV4, ASP4, REXSF, AIGAIM, ProATCx, GSX 

I9-9900k @ 5.0; Asus Maximus XI Hero; Asus Strix GTX 1080ti; 32GB G.Skill Ripjaw DDR4 3600; 2X Samsung 1TB 970EVO; NZXT Kraken X63; Seasonic Prime PX-1000, Single 32" 4k Monitor 



 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    22%
    $5,600.00 of $25,000.00 Donate Now
×
×
  • Create New...