Just me?

[forthbridge]

Hey guys......

Brand new FS9 installation on the new PC. All aircraft (and FSUIPC) copied over from the other installation. All fine... except........

At normal loads, the VC10 does not rotate at the same point it does on the old system. At EGQL, at takeoff power if lifts around the arrestor gear (give or take) in still air. The same A/C on the new machine drags and barely gets off the deck in the whole runway length.... in reality it would take out the boundary fence and approach lights.......

......on the other hand, the 1-11 lifts off a LOT more quickly than on the old system (about 2 seconds to be exact).

Now, except for FS itself, (newly installed) I pulled everything else over. When I noticed this, I deleted the VC10, and installed it from the downloaded files. Still the same.

FSUIPC is the same version as the old machine.

[TSR2]

Jim, Just out of curiosity.... does the same issue occur with the 1-11 and Trident? I know Ant was having difficulty get these to fly on the numbers last week and he hadn't installed them before

[forthbridge]

HI Ben

I've not reinstalled the Trident yet (will do so shortly) - but the 1-11 is actually quicker off the mark.... it goes by the numbers in the old (and new) installation, except on the new machine, it lifts (at the same speed) but gets there more quickly (around 2 secs) - very noticeable.

The 10 also lifts at the correct speed, it just takes longer to get there....

[DaveB]

Hi Jim..

I was going to post something about taking off on the old pc and flying on the new one but won't

I've noticed various differences between systems over the years.. moreso of late with USB 2.0 being common and although backward compatible with 1.1.. things just arent the same. There is no noticeable difference between say my XP2400 and my XP3200 but there is (or was before it died) a much bigger difference between the XP3200 (which is also a mix of USB 1 and 2) and the DualCore system. FSUIPC's are the same.. models are the same.. joysticks are the same (M$ SW Precision Pro) but an example of a very noticeable difference is the simulated prop braking on the Vanguard. It works just dandy on the XP3200 but not at all on the DualCore. Why??.. who the hell knows.. I certainly don't. One might expect things to react faster on a much faster system but I can't see any logical reason for something not working at all

Good luck in getting it sorted mate.. if indeed it can be

ATB

DaveB

[forthbridge]

Yo Dave

I did think 'system speed', but there isnt' all that much of a difference. I'm still tinkering, and in reality it isn't a major deal, I can just put a little extra power on... no costs for wearing out the engines on FS - otherwise, they fly the same...

[DaveB]

I remember years ago putting an old favourite 'Wolfenstein' (the DOS 6.2 version) which I'd played the @rse off (and scared myself too) on my 486SX25 onto the new Intel Pentium 50 (Classic.. first of the line 5v turn the central heating off jobbie). It ran so fast on the P50 it was unplayable

ATB

DaveB

[TobyV]

Hi Jim..

I was going to post something about taking off on the old pc and flying on the new one but won't

I've noticed various differences between systems over the years.. moreso of late with USB 2.0 being common and although backward compatible with 1.1.. things just arent the same. There is no noticeable difference between say my XP2400 and my XP3200 but there is (or was before it died) a much bigger difference between the XP3200 (which is also a mix of USB 1 and 2) and the DualCore system. FSUIPC's are the same.. models are the same.. joysticks are the same (M$ SW Precision Pro) but an example of a very noticeable difference is the simulated prop braking on the Vanguard. It works just dandy on the XP3200 but not at all on the DualCore. Why??.. who the hell knows.. I certainly don't. One might expect things to react faster on a much faster system but I can't see any logical reason for something not working at all

Good luck in getting it sorted mate.. if indeed it can be

ATB

DaveB

Not sure if it would effect flightsims, and if it did, not to this noticeable degree, but what you describe - between different processors and systems does exit. In my job, I run 3D RANS codes (Computational Fluid Dynamics, theres a nice article on wikipedia if you're having trouble sleeping) and depending on what machine and what platform its been compiled on, the same job can give different answers due to the way in which floating point is handled.

Stupid suggestion for the original problem, but do you have a joystick throttle and is it fully operational and correctly calibrated? If your throttle is physically at 100% but either due to calibration probs or worn potentiometers is actually at a lower value, that'd explain why the aircraft rotates at the right speed but takes longer to get there.

[Garry Russell]

I have a similar thing to that Toby but on 0 power

When I start up multis they swing into the dead engines until those start and stop the swing

The throttle is fully closed but F1 stops the swing happening

So perhaps if F4 was tried that should give full power and highlight any problems there

Garry

[TobyV]

Hi Garry,

The way I used to solve this was to recalibrate the joystick throttle axis and when it asks you put push it fully forward or fully back, you don't quite. That way when it is at its limits, then you are guaranteed full throttle or idle throttle.

Toby

[Garry Russell]

Makes sense Toby

I'll try that

Garry