-G
I am not sure but would think that is just the default flight/aircraft that
FSX ships with, and once you change it , it is changed?
Perhaps there is a way to reload it , hopefully if there is someone will
know.
--
Don
I just reset mine back to the default by accident. I had changed the
default startup to a Cessna 150 at SeaTac and Rwy 34 using "15 minute
updating" real weather. The next time I loaded the program, FSX gave
me an error..."Unable to load startup flight, reverting to default
startup"...
So now, mine is back to the original "Trike". Wondering if saving
using real weather update may have been the reason.
Prop
"Gregory" <flights...@bkwds.comcast.net> wrote in message
news:q125b5l9bp5a4shoc...@4ax.com...
>
delete your FSX.cfg file
"Gregory" <flights...@bkwds.comcast.net> wrote in message
news:q125b5l9bp5a4shoc...@4ax.com...
>
"Danny" <drm...@yahoo.com> wrote in message
news:h8u7f0$5iv$1...@news.eternal-september.org...
>Obviously, Danny's reply is better because it doesn't delete ALL your settings. :)
Was thinking of moving the CFG file to a / -BAK folder and letting FSX
build a new one. Something has gone `south� with the throttles. Funny
thing is.. the raw data looks really smooth. Where the blazes could the
spikes and interference be coming from?
-G
"Gregory" <flights...@bkwds.comcast.net> wrote in message
news:b1c5b5hlbgj7sle9a...@4ax.com...
"Gregory" <flights...@bkwds.comcast.net> wrote in message
news:b1c5b5hlbgj7sle9a...@4ax.com...
Bad slider or pot? Bad USB port or connector. Usually, spikes and
interference are a hardware issue.
You are talking about electronic spikes versus graphical artifacts I assume.
Not easy to answer. I tried three configurations..
1) Quad connected through CH Controller Manager
2) Quad connected direct to Xp via USB
3) Quad direct to Xp with new, regenerated fsx.cfg
The first thought would be an interfering controller definition. Could
not find any. Also cleared FSUIPC settings. Maybe I'll pull the
Flightstick, and also plug the Quad into another USB port, but
doubt that would matter.
The Saitek throttles shipped today and will arrive next Mon or Tue.
There's a 30-day return for the CH product via Amazon.
-G
P.S. yes.. they aren't just VC artifacts. The AC goes into REV in the
right engine and then goes nuts on the ramp, with spins and even a tail
strike resulting in crash.
"Gregory" <flights...@bkwds.comcast.net> wrote in message
news:02a7b5p1js0r90ejn...@4ax.com...
Did you check for axis conflicts? Something that's set in FSUIPC, the CH
Controller and/or FSX itself?
IIRC that type of wild behavior can be caused by that type of conflict
Look in your standard.xml file in the Controls folder and see if anything
looks strange. You could also try renaming the standard.xml file and let FSX
rebuild it and see if that helps.
>> P.S. yes.. they aren't just VC artifacts. The AC goes into REV in the
>> right engine and then goes nuts on the ramp, with spins and even a tail
>> strike resulting in crash.
>
>Did you check for axis conflicts? Something that's set in FSUIPC, the CH
>Controller and/or FSX itself?
>
>Look in your standard.xml file in the Controls folder and see if anything
>looks strange. You could also try renaming the standard.xml file and let FSX
>rebuild it and see if that helps.
Good idea you had. Standard.xml was a mess, so I moved it to the -BAK
folder and a new one was generated when FSX started. No joy.. still have
erratic RIGHT throttle lever. So there's been no FSX activity this
weekend (yet). Last ditch effort will be to rename FSUIPC.dll to .dl_
and start-up default King Air.
The other throttles are going to arrive in a couple days.
-G