Jump to content
The simFlight Network Forums

emersonbattle

Members
  • Posts

    29
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Maryland

Recent Profile Visitors

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

emersonbattle's Achievements

Newbie

Newbie (1/14)

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

Recent Badges

0

Reputation

  1. The real Embraer has a "steep approach" option offered by the manufacturer. That is what the original poster is referring to. Simply configuring the aircraft fully before the glide slope is not the correct answer at an airport like London City because the glide slope itself is at a steeper angle than most other airports are.
  2. Never mind. There is no mention of it at all in the manual. I don’t feel that using one add-on should have an adverse effect on other add-ones. This product just doesn’t seem worth the hassle. I had high hopes pinned on the service pack’s release, but it just feels like one thing after another. I bought this pretty much as soon as it was released and I was really excited, but after the initial download, the hot fix, and the service pack, this thing still has fairly basic problems that are left to the end user to work around. I just think I’ll avoid FeelThere purchases in the future. I appreciate your replies though.
  3. I’m not sure how to do that… Additionally, does doing so have an impact on how I use ChasePlane and all the other aircraft in the sim?
  4. Middle mouse-click isn’t working. It opens the ChasePlane pop-up menu. Is there a workaround for this?
  5. I have the latest SP installed, but the pushbuttons in each of the rotary knobs (Baro Standard Set, Flight Director, Heading Sync, Feet/Meters) don't seem to work. Anyone having similar issues?
  6. So, it's almost 5 pm here and I'm just now turning my computer on for the first time since sending the post quoted above. Something told me to just turn on the sim to refresh myself about where I stand before I go removing drivers and uninstalling again and for some reason.... IT WORKS! I have no idea what may have changed, but with the Thrustmaster drivers still installed (the same ones that didn't allow ANYTHING to register w/FSUIPC yesterday) and what I think are a few errors/duplicated entries in the Joy Names section, all of my peripherals are responding in FSUIPC. So obviously I'm going to just leave everything as-is. Thank you all for your support and your great product. You were correct Pete, P3D doesn't REQUIRE FSUIPC to function, but what I meant in my earlier post is that P3D itself surely doesn't offer the functionality needed to manage aircraft from PMDG, FSLabs & the like on its own. You've definitely created a "must have" piece of software for the MSFS/P3D comunity. As someone whi's been using it on one FS version of another for the past 15 years... I'm glad to have everything back up and running again. John and Pete, thank you both for your help, it's VERY appreciated and I hope you didn't pull out as much hair as I did trying to fix my problem. I've attached a few files for you to look at (only if your curious). Maybe the reason it works now is clearer to you than it was for me. FSUIPC5.ini FSUIPC5.JoyScan.csv FSUIPC5.log
  7. Ok… Now it’s almost midnight here. I’ll try tomorrow to delete the drivers and really on the default ones. It’ll likely be sometime in the evening your time. I know you’re all out of ideas, but once I remove the drivers, if it still doesn’t work, is there some way I can just remove everything FSUIPC “knows” so to speak… then maybe have it re-learn what it knows about my setup? Or otherwise can I COMPLETELY remove FSUIPC from my system and just try again as though it was the first time it had been installed. I'm at a loss for ideas. I NEED to fix these to get my sim playable again, and I’ve seen you work your magic in these forums for years now. I mean no disrespect to the Thrustmaster staff, but I honestly think have a better chance under your teams guidance than theirs.
  8. No worries! I actually need to get going too. I'll be back later tonight but it'll be early morning in Europe. I have good news and bad news though. Good: In the Device Manager window I was eventually able to distinguish between devices plugged directly into the computer, linked via bluetooth and those running through USB hub. From there I just disconnected everything from the hub EXCEPT the throttles. Then I was able to locate the proper HID-compliant game controller and USB input device. I removed them and continued with the instructions as posted. Bad: It didn't fix my problem and now I can't get my joystick to register inputs in FSUIPC either. While running the steps you called for earlier, I did realize that Thrustmaster updated their drivers, so when I re-installed the drivers they were a newer version but that was unavoidable. I don't have copies of the older drivers. I ddon't know that that was a contributing factor, I just thought I'd mention it to you. I've also included the lastest FSUIPC.ini file as well as the latest log file. I'm not sure where to go from here but I really need to find a fix. Even if it means starting over/loosing data or settings. At this point P3D is almost unusable until I get this fixed. : - ( FSUIPC5.JoyScan.csv FSUIPC5.ini FSUIPC5.log
  9. I know windows recognizes the devices. some of the buttons on my throttle are used used to manipulate Chaseplane and that works with no problem. I am not above just removing all input devices and starting over from scratch if you (a) think that would solve the problem and (b) can talk me through at least enough of it to not break anything else. I found some Thrustmaster drivers. I'm removing them now. Enjoy your meal!
  10. Stuck on step 1... Can you help me find an adress or some sort of unique identifier for my Warthog devices please? Windows is listing everything in very generic terms. I need to figure out which ones to uninstall from the lengthy list. View photo to see what I mean. I know I should be removing 2 HID-compliant game controllers and two USB input devices. I just don't know which ones.
  11. Thanks! I'll be standing by. In the meantime, can I move forward with adding button and axis assignments to my joystick, or is that a waste of time? Is the work I do between now and your reply likely to be overwritten with the fix?
  12. And... yes, that was a cut & paste from FSUIPC.ini generated AFTER I removed everything as you asked. I just went back to compare them and I see it was identical to the attachment at the top of this thread.
  13. [JoyNames] AutoAssignLetters=Yes 0=Joystick - HOTAS Warthog 0.GUID={6F3BE990-5696-11E7-8001-444553540000} 2=Mad Catz Pro Flight Rudder Pedals 2.GUID={882C2890-5906-11E6-8005-444553540000} 3=Razer Tartarus V2 3.GUID={50E9F090-52E4-11E8-8001-444553540000} 4=Joystick - HOTAS Warthog 4.GUID={50F980F0-52E4-11E8-8005-444553540000} 6=Wireless Controller 6.GUID={F2B66560-1B43-11EA-8002-444553540000} A=Joystick - HOTAS Warthog A.GUID={6F3BE990-5696-11E7-8001-444553540000} B=Mad Catz Pro Flight Rudder Pedals B.GUID={882C2890-5906-11E6-8005-444553540000} C=Razer Tartarus V2 C.GUID={50E9F090-52E4-11E8-8001-444553540000} D=Joystick - HOTAS Warthog <--------- I suspect this to be a part of the problem D.GUID={50F980F0-52E4-11E8-8005-444553540000} E=Wireless Controller E.GUID={F2B66560-1B43-11EA-8002-444553540000}
  14. No joy. Still the same result. : - ( What are the drastic steps you had in mind?? I'm willing to dig into regedit if you can talk me through it.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.