[Controls Not Recognized]

Thanks for all the help John!

[Controls Not Recognized]

Thanks John, I did as instructed above and I was able to get a test profile set up...I've attached the files here.

FSUIPC7.iniFSUIPC7.logFSUIPC7.JoyScan.csv

[Controls Not Recognized]

Thanks John, a few questions to make sure I'm doing what I should be:

- When you say make a back up of my registry, do you mean by using the export inside regedit and then exporting all?

- How do I create a new reg file?  Is that done inside regedit?  I see the ability to create a new key?  Or do I just create a text file, put that content in it, the rename it to a .reg file?

Thanks,

Dave

[Controls Not Recognized]

Looks like I spoke too soon, after a successful flight earlier today, tonight my controls are not working again.  I'm really not sure what's going on here, it seems like something is making up additional controllers that don't exist, for example it's showing four X-Box controllers when I only have one?  Two TQ-6's when I only have one?  

I tried starting from fresh with a new FSUIPC7.ini file which is attached here and shows the extraneous controllers.

FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log

[Controls Not Recognized]

That seems to have done the trick, thanks!

[Controls Not Recognized]

OK thanks John, I'll try starting with the FSUIPC6 file and report back.

Dave

[Controls Not Recognized]

Thanks John, I couldn't find any specific VirtualFly devices drivers.  I had a look at the vJoy config and it only shows one device connected which I would expect is my Brunner Yoke (the reason I have vJoy installed).

I'm thinking this means I'll need to go the registry route?

For what it's worth I had a similar issue in FSUIPC6 with duplicate TQ6 entries in my FSUIPC.ini after I tried to set the axes up in P3D.  I deleted the extra entry but took what I assume is the device number from the new entry and changed it in the old entry and that seem to solve my issues there.  Here's an except from FSUIPC6 of my axes configuration.  3X and 3Y are where I inserted the number 3 from the new entry that was created:

[Axes.Airbus2 HOTAS]
RangeRepeatRate=10
0=0X,256,F,65764,0,0,0    -{ TO SIM: AXIS_RUDDER_SET }-
1=0Y,256,F,65762,0,0,0    -{ TO SIM: AXIS_ELEVATOR_SET }-
2=0U,256,F,66387,0,0,0    -{ TO SIM: AXIS_LEFT_BRAKE_SET }-
3=0V,256,F,66388,0,0,0    -{ TO SIM: AXIS_RIGHT_BRAKE_SET }-
4=3X,256,F,66420,0,0,0    -{ TO SIM: AXIS_THROTTLE1_SET }-
5=3Y,256,F,66423,0,0,0    -{ TO SIM: AXIS_THROTTLE2_SET }-
6=3R,256,F,66382,0,0,0    -{ TO SIM: AXIS_SPOILER_SET }-
7=4X,256,F,65763,0,0,0    -{ TO SIM: AXIS_AILERONS_SET }-
8=4Y,256,F,65762,0,0,0    -{ TO SIM: AXIS_ELEVATOR_SET }-
9=5X,256,F,65763,0,0,0    -{ TO SIM: AXIS_AILERONS_SET }-
10=5Y,256,F,65762,0,0,0    -{ TO SIM: AXIS_ELEVATOR_SET }-

This all seemed to start recently when I was playing another game that required me to unplug my TQ6 and my Warthog HOTAS throttles because their inputs conflicted with the game controls.  Wen I plugged them back in the issues started.

Thanks,

Dave

FSUIPC7.JoyScan.csv

[Controls Not Recognized]

Hello, I  have two axes (my rudders and throttle/prop/mixture) not being picked up.  I successfully set up my first profile the first night I used FSUIPC7 night and calibrated my throttle quadrant and it worked fine.  Tonight it's not being picked up by FSUIPC at all.

FSUIPC7.ini FSUIPC7.log

[FSUIPC7 controls are not detected]

Hello, I also have two axes (my rudders and throttle/prop/mixture) not being picked up.  I successfully set up my first profile last night and calibrated my throttle quadrant and it worked fine.  Tonight it's not being picked up by FSUIPC at all.

 

FSUIPC7.log FSUIPC7.ini

[Cant change from LBs to Kgs.]

How did you fix this?  I am able to switch to kgs in the configurator but could never figure out how to switch the aircraft over.

[P3D v5 and v4 COMPATIBILITY- status post LM May 2020 hotfixes]

Sure here you go:

https://a2asimulations.com/product/a2a-rain-effect-for-p3dv4/

It’s in their store, though it is free.

[P3D v5 and v4 COMPATIBILITY- status post LM May 2020 hotfixes]

A2a has updated their windshield.dll file, available for download at their website.

[P3D v5 and v4 COMPATIBILITY- status post LM May 2020 hotfixes]

It seems like a lot of aircraft are having issues with blurry glass cockpit displays.  I haven’t tried this fix on the E-Jets but it looks like it works on a variety of other aircraft:

https://www.avsim.com/forums/topic/573601-real-air-gps-fuzzy-in-v5/

In short, go into the panel.cfg, under [VCockpit##] look for pixel_size= and change the entry to 2048,2048 or 4096,4096 and see if that makes things more crisp.

 

[E-170\190v3 Performance page keeps saying "Not INITIALIZED"]

Yes, if you’re used to the Boeing and Airbus way of doing things you’ll certainly encounter a few “gotcha” moments with the Embraer.

[P3D v5 and v4 COMPATIBILITY- status post LM May 2020 hotfixes]

Thanks, I have a gtx1070 with 8gb, based on my vram usage I couldn’t imagine trying to run v5 even with 4gb.

Of course as it was with out of memory crashes with P3Dv3 and earlier, no one addon will cause the crash generally, but in my case so far this is the only aircraft that I was using when I ran out of vram so far.  It’s early days, I’m sure this will all get ironed out. 

[P3D v5 and v4 COMPATIBILITY- status post LM May 2020 hotfixes]

22 minutes ago, follettj said:

Its extremely heavy on GPU memory in my initial looks, PMDG 737 runs at 3.0GB max but the e190/170 is running at high 4s aka 4.8GB.

This is the only aircraft I’ve flown so far where I ran out of VRAM.

[P3D v5 and v4 COMPATIBILITY- status post LM May 2020 hotfixes]

Hello, I was able to install and load the aircraft and it flies fine.  I noticed a greenish tint to the cockpit windshield that wasn't there in v4.  Not using any shader modifications or anything else like that.  This is in the E175 and is repeatable.

 

 

[P3D5]

That’s great news if it’s the only real issue, A2A is working away on that I’m sure.

[Repaints - Requests and New Releases]

@jhkayeYou have to go into the aircraft.cfg file and copy over one of the aircraft entries from another aircraft, then edit it for the Air Canada repaint info.  How this text wasn’t included in the repaint like every other repaint on earth is beyond me but I digress...

[Feelthere E170 V3 GSX profile]

Thanks!  I haven't been able to get the baggage vehicles to unload so this should fix that right up.

[Question before buying.]

I have a 32” monitor and using my usual MSAA settings it is very hard to read.  Using SSAA is a bit easier but SSAA is a known resource hog.  I’ve memorized which button is which after a few flights and programmed a chaseplane view to zoom in.

Annoying, but not show stopping in my view.

[Repaints - Requests and New Releases]

Great repaint Jeffery, thank you!

[UPDATE FROM FEELTHERE]

Thanks Vic, generous offers.  It's been so great to see payware developers step up and provide free or deeply discounted products during this unprecedented event, makes me very proud to be part of this great community of flightsimmers!

[Repaints - Requests and New Releases]

16 hours ago, Jeffrey S. Bryner said:

Thank you for catching it.

Best,

Jeffrey S. Bryner

That’s the easy part, thanks for painting it 😁

[Repaints - Requests and New Releases]

It’s posted now, if you do a search for TAP it’s the third result.