Jump to content

Archived

This topic is now archived and is closed to further replies.

Clutch Cargo

HELP! My P3D is possessed!

Recommended Posts

This is so bazaar, I just had to see if anybody else has come across this. When starting a flight, doesn't matter if it is a default aircraft or even a convert moved over from FSX, the plane automatically starts up on it's own, runs for 10 seconds or so, then stops. Then it repeats itself... starts up - runs a bit - then shuts down... even if I am flying! I can sit in the cockpit and watch all the animation happen. In the Cessna I see the key turn over and the throttle slides in to give power. Revs up the RPM starts to move then shuts off. Whaaaat?

 

It started, as best as I can tell some 24 hours ago. I installed one new add-on Aerosoft's USCitiesX - Las Vegas. I did have some problem getting it activated. So I assumed because I was installing it into P3D it was maybe some anti-pirating thing which screws up your flying in that area. So I uninstalled the program, and even started in an area way far away from Vegas. Same issue.

 

Right now I don't think I can even use P3D right now!?!? 10 years of simming and I have never seen this.

 

Clutch

Share this post


Link to post

Clutch, were you entertained as it is not allowed from the use of the licence according to P3D.......

 

Sorry guys, I could not resist.... :spiteful:

Share this post


Link to post

Clutch, there seems to be a conflict in your controls, are you using fsuipc??

Share this post


Link to post

In over 20 years, never seen anything like this, I have no idea.

I uninstall and start from ground zero, or hire an exorcist ...

 

João Alfredo

Share this post


Link to post

Very good insight, Will. Yes I do have a reg version of FSUIPC. That too, 24hours ago was working perfectly. But when I pull up the FSUIPC screen to the Axis Assignment tab the IN and OUT fields are freaking out with thousands of numbers all zipping past my eyes. Pressing rescan does no good. Cannot get the numbers to stop even for a second.

 

So yes, that does appear to be some conflict. And I have experienced that in the past (like many of you perhaps), when you press or flip a switch something unintended happens due to a conflict. That I can grasp. But I am NOT touching a button or axis or switch. Again, happening on its own. It's like I am watching a recorded video of someone starting up an aircraft taxi a bit, then shut it down. That's what has my head scratchin' (and I'm a little scared too... it's the work of the devil!!!! :diablo: ).

 

May FSUIPC got corrupt? I'll move out my custom .ini to see if that does anything.

Share this post


Link to post

Try unplugging your controllers, just for the heck of it. I dont believe FSUIPC would be the problem but could have a stuck controller switch or keyboard button? devil, naaa, gremlins, yesss

Share this post


Link to post

Go into your P3d setup screen and make sure your "enable controls" option is unticked.

 

You do get odd problems when P3D and fsuipc are trying to control things.

 

Share this post


Link to post

You do get odd problems when P3D and fsuipc are trying to control things

 

I've not noticed any problems? If one did think,for some reason it was FSUIPC. Remove the FSUIPC.dll from the modules folder and restart P3D.

Share this post


Link to post

You were lucky enough not to have conflicts then.

 

I have all my controls assigned via fsuipc and default controls disabled.

 

If for any reason fsx controls are enabled, you have two platforms trying to control the same hardware.

 

It is a very old and common sensicle problem.

 

Share this post


Link to post

I run both FSX ,P3d and FS2004 with no probs and they shouldn't share each other module folder. I even use the same FSUIPC.ini in both sims. You best ask Pete what your problem is.

Share this post


Link to post

Alright.... the fix is a bazaar as the problem. Are you ready to hear what fixed it?........

Share this post


Link to post

I'm a little embarrased and dumbfounded. I shut everything down, Re-booted. Bang... everything back to normal :Shocked: ??? No FSUIPC issues, no aircraft taking off on their own issues, no 3rd party issues. That's it... I'm headin' to the kitchen, grabin' an Octoberfest beer and gonna go watch the boob tube for a bit. I think I need a rest.... :crazy:

Share this post


Link to post

Glad you got it sorted! I feel obligated to inform you that it's "bizarre" rather than "bazaar" unless you consider your computer a market of some sort.

 

-stefan

Share this post


Link to post

october beer and boob tube? I do not think that's how it's celebrated : )

Share this post


Link to post

Remember the three "R" 's of computers -

 

When all else fails - Reboot - if that doesn't work - Reinstall and if that doesn't work - Rebuild

 

actually there is a fourth - Rant!!!

 

:)

Share this post


Link to post

Seems to be most folks 1st step. :)

 

:LMAO:

Share this post


Link to post

Well, I woke up this morning, fired up good ol' "Sim" after a night of head-scratchin' and guess what came back.... yep, good ol' "possessed Polly"!!! Same thing happening all over again. So I took your advise on the post above and employed step #4 - RANT :t0116: . But that didn't seem to help much. So I created a new step of the four "R"s and made step #5 - REVIEW.

 

Thinking to myself what was happening thought it appeared the aircraft was going through and Auto Startup and Auto Shutdown. Doubled-checked all the default buttons and axises in P3D to make sure they have all been deleted since I use FSUIPC. I then went through each piece of hardware and DISCOVERED my Saitek #1 throttle quadrant had a loose connection. For those not familiar with Saitek's Yoke, the throttle quad that comes with it uses an old-fashion mini-din6 (like AT keyboard connections). Due to my cockpit layout I have a mini-din extension cable in-line, and though it was connected it was loose.

 

And I just happened to assign Auto-starts on some those Quad buttons and Fuel Run/Cutoff on a couple more. Apparently, the loose or intermittent connection was causing the quad buttons to cycle through all the assignments continuously via FSUIPC. So I was getting not stop starting/stopping and FSUIPC was freaking out as well.

 

All it took was good snug "push" shut of those connectors and everything went immediately back to normal. Yea, I can fly again! :yahoo: Just thought I'd post in case someone else come across similar issues.

 

CLutch

Share this post


Link to post

Another mystery solved!!

 

hate it when it's a loose cable, much more challenging when it's random failures caused by rogue code!! LOL

 

Vic

Share this post


Link to post
×
×
  • Create New...