FSDreamTeam forum
October 21, 2014, 09:41:44 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: KIAH has been released!
 
   Home   Help Login Register  
Pages: [1] 2 3 ... 10
 1 
 on: Today at 08:57:10 AM 
Started by vc-10man - Last post by virtuali
However, if my scenery.cfg is corrupted, how is it that (a)I do not get a scenery error flag when FSX loads, and(b) how come I can select any or all the airports including all my non-FSDT add-ons without any problems?

There might be two possible explanations for this:

1) FSX doesn't use the standard Windows routine to read .INI files, but has its own parsing routine, which has been made more robust against syntax errors, so it's able to just skip the problematic area, instead of refusing the read the file or, probably, the sections after the corrupted one.

Both GSX and (likely) Flightsim commander, use standard (provided either by Windows or by some standard library) .INI parsing routines, that are more formally correct, so they treat as errors what FSX is able to accept.

OR

2) BECAUSE of FSX is running in Compatibility mode, it's reading from another scenery.cfg file, instead of the one running under C:\ProgramData\Microsoft\FSX

Again, not possible to know without having a look at your scenery.cfg and checking if it's really corrupted.

 2 
 on: Today at 06:43:54 AM 
Started by psykie - Last post by Dave_YVR
 Seriously?

 http://www.fsdreamteam.com/products_gsx.html

 3 
 on: Today at 12:41:40 AM 
Started by psykie - Last post by psykie

Quote
The download has always been freely available, and there's only one place you can download it.

Where?

Matthew

 4 
 on: October 20, 2014, 11:58:43 PM 
Started by vc-10man - Last post by vc-10man
Yes, in a way, as FlightSim Commander is not related to FSDT products, I saw no point in broaching it here.

However, if my scenery.cfg is corrupted, how is it that (a)I do not get a scenery error flag when FSX loads, and(b) how come I can select any or all the airports including all my non-FSDT add-ons without any problems? Surely, logic dictates if the scenery.cfg is corrupted, then I would not see any of those airports. Or maybe I have this concept wrong?

 5 
 on: October 20, 2014, 11:22:19 PM 
Started by Spartan0536 - Last post by Spartan0536
I am very pleased to hear this considering I just purchased (within the last 48 hours of this posting) KFLL and KDFW from PCAviator. I look forward to newer products from FSDreamTeam and I hope to see a KFLL V2 in the future. Thanks for taking the time to reply to my thread Smiley

 6 
 on: October 20, 2014, 11:16:08 PM 
Started by Sludge - Last post by hd764jvgd843
Hello jimi08,

sorry for confusing you with sludge. Thanks for answering all of my questions in such depth. I can see now that you have obviously spend a lot of time, effort and thinking to get the Hornet's flight behavior as realistic as possible, as it already is. I am merely beginning to scratch the surface here and I hope I could provide some useful information and thoughts to get things even better. The reason why I have tried to provide such an in-depth evaluation and review of your Hornet is that I really like to fly with it because it handles far more realistically than any other version I have stumbled upon. You have really done a superb job modeling the flight characteristics with your FCS so far!

Concerning the oswald_efficiency_factor, the LEXs do not increase or decrease the lift efficiency of the wings itself, they just allow for higher AOA's without going into stall (at the cost of a slightly higher drag), thus making the plane more maneuverable. In order to retain proper handling/rolling abilities at a high AOAs the wing was given a relatively high wing twist (a little more than 4 degrees), so the physical AOA at the tip of the wings (where the ailerons are) is lower than near the fuselage and does not stall as fast as the rest of the wing during high AOAs. So I would stick with the original 0.8 value here, maybe 0.85 but not higher. The cross section of the wing itself is much too flat for an oswald factor of 0.95 which could create the lift efficiency of a high performance sail plane.

Concering the "Impact damage threshold" values in the [Contact_points] section, I do not have any references here, but I found the original values for the gear much too sensitive, barely being able to land on a runway, not to speak of a carrier. Watching several carrier landing videos and comparing them with my own attempts I felt that values between 2500 and 3000 seemed to be realistic here. All other "impact damage threshold" values (wingtips, bottom, top) I left unchanged.

Concerning the "afterburner stages", six seem to be the correct number for both engine types (old and new ones). But as you have pointed out they are quite noticeable when in afterburner mode. I do not know if the transitions are felt that way in reality, but I found it to be a nice feedback when to enter/leave AB mode in the simulator. I have read somewhere that the thrust leavers in reality have a clearly defined and noticeable point so the pilot always knows intuitively weather AB mode is engaged or not.

I hope this helps.

Best regards...

Peter

 7 
 on: October 20, 2014, 11:11:12 PM 
Started by Maia Soares - Last post by virtuali
Read the other topics about this,but none had the solution to this problem.

That's not the case, this user had that problem, and he fixed it by reinstalling FSX:

http://www.fsdreamteam.com/forum/index.php/topic,8326.15.html

The problem is not Couatl.exe, it's just a victim of problem with the FSX install, like corrupted missing/files, or possibly some runtime libraries needed by both FSX and Couatl.exe that are missing/corrupted/wrong/outdated, and if reinstalling or repairing fixes it, it's clear proof Couatl.exe crashing was the effect, not the cause.

 8 
 on: October 20, 2014, 11:08:01 PM 
Started by vc-10man - Last post by virtuali
Which explains why when I tried to install FlightSim Commander, it would not read the Scenery.cfg.

You would have made my work easier if you said something like this:

"why BOTH GSX AND FlightSim Commander can't read my scenery.cfg anymore ??"

Were you worried that, since it's would have been clear your question didn't have anything to do with GSX, and it's just a generic question about fixing a problem with the scenery.cfg, you wouldn't get any help ?

First, you must understand if the problem is the scenery.cfg itself being corrupted, or it's just your system using the wrong one, this can only be checked by looking at it.

 9 
 on: October 20, 2014, 11:05:38 PM 
Started by Maia Soares - Last post by Maia Soares
Anytime I try to activate the GSX,I Get an APPCRASH with Couatl.exe.Also,after this,the Addon manager and Couatl disappear from the top menu.

Read the other topics about this,but none had the solution to this problem.

 10 
 on: October 20, 2014, 10:47:38 PM 
Started by vc-10man - Last post by vc-10man
Thank you for that explanation.

Which explains why when I tried to install FlightSim Commander, it would not read the Scenery.cfg.

Is there a way to restore/repair it?

Pages: [1] 2 3 ... 10
Powered by MySQL Powered by PHP Powered by SMF 1.1.20 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!