Convair Delta Wing Test

WarHorse47 said:
I assume these latest issues are more with P3D?

I've encountered no issues with FSXA, but did note there were no lights externally or internally.

My last flight was uneventful. I took off from Edwards on Rwy 4R and climbed to 40,000 feet at full AB. After turning 180 degrees and headed back to KEDW, I watched my fuel which was at 50%. I landed with the "Bingo Fuel" warning. Hard to slow it down to a reasonable landing speed, so I took up most of the runway before stopping and taxing back to parking. Lots of fun. :very_drunk:
Click to expand...

+1 I find that it flies well until I try for a hi-speed run. It start doing a rather weird wobble up in the high 500Knots indicated airspeed. Back to normal after lowering the speed. I stuck my first center-line landing at McClellan in Sacramento. Landing speed was about 180, luckily a very long runway.
 
Negative, we have users in FSX, FSXA, P3Dv3, and FSX Steam Edition experiencing the issue. I think 4-5 users across these sims have the take off issue.

The trans-sonic behavior is part of the expected behavior at those speeds.
 
WarHorse47 said:
I assume these latest issues are more with P3D?

I've encountered no issues with FSXA, but did note there were no lights externally or internally.

My last flight was uneventful. I took off from Edwards on Rwy 4R and climbed to 40,000 feet at full AB. After turning 180 degrees and headed back to KEDW, I watched my fuel which was at 50%. I landed with the "Bingo Fuel" warning. Hard to slow it down to a reasonable landing speed, so I took up most of the runway before stopping and taxing back to parking. Lots of fun. :very_drunk:
Click to expand...

There are no exterior lights. This was a day-time, fair wx test machine.
The gauges are back-lighted.
 
@MrZippy

Yes, you're starting to encounter the transonic region. gets a little shaky, but still controlable. If it were an F-86 you'd notice a wing dip and control freeze approaching Mach 1.
 
WarHorse47 said:
I found the switches on the lower left panel and just was curious. Thanks.
Click to expand...

As was mentioned in the build process, this aircraft was a product of borrowed parts from other aircraft at the time of its build.

I mirrored that strategy by borrowing the VC from my other projects. :)
 
Again, the affected users should check their FSUIPC for any friction fixes. Or find another common demonimator, like Accu-Feel or so.
 
Bjoern said:
Users with issues should check their FSUIPC for any ground friction mods.

Aircraft.cfg contact points are valid, I assume?




Yeehaw!
Click to expand...

Bjoern,

Yes, a good point re: friction settings.

I set the original contact points from gmax coordinates, but will re-check to ensure all is well.
 
Another option to test for affected users, comment out this line in the contact points:

point.3= 2, -16.335, 0.0, -2.67200, 2600, 0, 0.446, 0, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000,0

to look like this:

//point.3= 2, -16.335, 0.0, -2.67200, 2600, 0, 0.446, 0, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000,0

EDIT:

And change these two parameters in the Contact Point Section:

static_pitch = 1.36
static_cg_height = 6.900
 
That line mentioned above is a skid at the tail, if you drag it generally it will leave sparks. Way over rotation on takeoff or more likely tail strike on landing. You really can't lift the nose wheel till over 100 knots, so I expect not the problem.
 
We had another plane under P3D Beta test once that somehow got lat/long position locked and would only go straight up and down. Anything is possible in the sims.
 
We're using XML Tools. Doesn't that require .net framework to be installed? depending on which version 32 or 64 bit....could that be an issue causing something like this?
 
The .net framework version may have something to do with it, but i dont know enough to be sure. What I do know is that the things your exploring would all have global effects, (i.e. everyone would have them ) but thats simply not the case as some of us have no problems at all..
If i'm reading correctly, most of the problems are happening with FSXA. I'm running FSX:SE and dont see the problems, so i'm curious what the changes were from accel to SE. I believe that youll find the issue in those changes somewhere..
 
warchild said:
The .net framework version may have something to do with it, but i dont know enough to be sure. What I do know is that the things your exploring would all have global effects, (i.e. everyone would have them ) but thats simply not the case as some of us have no problems at all..
If i'm reading correctly, most of the problems are happening with FSXA. I'm running FSX:SE and dont see the problems, so i'm curious what the changes were from accel to SE. I believe that youll find the issue in those changes somewhere..
Click to expand...

I'm running FSX with SP1 And SP2. The aircraft (definitely not me) performs flawlessly.
 
I'm using P3D v4.2 on windows 10 and do have the problem. I have XML tools and net framwork. I switched to RR's 106 air file and the planes flies nicely.
 
You must log in or register to reply here.
Back
Top