• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX Acceleration Pack

scruffyduck

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,981
Country
unitedkingdom
Putting this in the General Forum.

I have just installed this and had quite a few problems.

  • The installer did not tell me or offer that I needed a later version of DirectX9. You need to latest runtimes from microsoft.
  • On getting FSX to start it gave me an error 1-80004005 that it could not activate on line. This needs a registry edit to overcome. See the notes below
  • If you have AFX and FSUIPC 4 then get the latest versions as they may cause FS to crash once it does load


This is a copy of a post that originated on AVSIM and was reposted on Microsoft Forums to deal with the activation error:

I got some help from a gent on the AVSIM forum and he suggested editting the registry as follows:

1) with regedit, located this entry:

HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\CLASS\{4D36E967-E325-11CE-BFC1-08002BE10318}

2) edit your UpperFilters key. For FSX and their validatin system, they expect it only reads "PartMgr". In your case, there is great chance it shows something more. In my case, it was reading:

GoBack2
PartMgr
SiRemFil

3) change the registry to read only "PartMgr"

4) start FSX, you should now be prompted with the activation dialog, proceed and let FSX start, then exit FSX.

5) edit back the registry key with your previous content

6) exit regedit, and start FSX again, it should all be fine by now!
Click to expand...

This also worked for me. If you need to do it then remember to put the original data back!!! - I forgot for a while :o


Finally I have found at least one of my airport 'AFCADs' that now have problems with the Accel pack installed. The runway is now partly below the terrain. I have not tested any others as yet and it might be an isolated incident. However it may be that the Accel Pack contains something that has modified the terrain engine or some other things related to altitude settings for airports.

So far I am not impressed..........
 
scruffyduck said:
Finally I have found at least one of my airport 'AFCADs' that now have problems with the Accel pack installed. The runway is now partly below the terrain. I have not tested any others as yet and it might be an isolated incident. However it may be that the Accel Pack contains something that has modified the terrain engine or some other things related to altitude settings for airports.

So far I am not impressed..........
Click to expand...

I had to help a friend with a his KERI that had the same problem. I used my new KERI CXV file and fixed the problem. Do you have a CVX file from previous version?
 
sparker256 said:
I had to help a friend with a his KERI that had the same problem. I used my new KERI CXV file and fixed the problem. Do you have a CVX file from previous version?
Click to expand...

It is an edit of the stock airport with no changes to the polygon or ARP altitude. It's actually the airport I am using to test the features of Airport Design Editor. I need to do some more checking but I need to get myself into the correct frame of mind :)
 
I must have been very fortunate, Acceleration installed and activated first time.

I find it a great improvement over SP1 and get even better frame rates when using the DX10 preview. Of course there are texture problems with FS9 aircraft in DX10, but I think a change to 32 bit textures should fix most of these.

George
 
I think that the airport problem is mine and not the Accel pack. However I am still curious as to why it worked pre Accel but not after :confused:
 
Finally I have found at least one of my airport 'AFCADs' that now have problems with the Accel pack installed. The runway is now partly below the terrain. I have not tested any others as yet and it might be an isolated incident. However it may be that the Accel Pack contains something that has modified the terrain engine or some other things related to altitude settings for airports.
Click to expand...


It seems the issue I had is maybe that runways no longer create flattens. Putting an apron under my test runway (as suggested by Jim Vile) resulted in the runway re-appearing. I do not have an airport flatten at this test airport
 
Well, if you still wander of what could possibly be wrong, I can just confirm having the same problem, no matter which programme I use. What I tried to do was to correct stock
FS X airport to an altitude that would fit better into a high res. mesh, it's a matter of 1.75 meters. I made a new flatten to that altitude using KML, tagged my poly "Airport_Backgrounds_Flatten", gave all of the elements (ARP, runway, starting locations) a new walue that is higher by mentioned 1.76 m and ended up with aprons that are actually visible, but made themselves sort of a channel that lies, yes, you guessed it right, precisely 1.75 meters below the flattened terrain, but runway isn't wisible, since I didn't put anything below it and I'm 100% certain, that, if I put an apron below the runway, I'll get the same result as with aprons - visible surface burried into the ground.

And, Jon, as far as I can understand the situation, that "maybe" is not needed, since runways definitely don't produce flattens anymore.
 
Last edited:
adr179 said:
Well, if you still wander of what could possibly be wrong, I can just confirm having the same problem, no matter which programme I use. What I tried to do was to correct stock
FS X airport to an altitude that would fit better into a high res. mesh, it's a matter of 1.75 meters. I made a new flatten to that altitude using KML, tagged my poly "Airport_Backgrounds_Flatten", gave all of the elements (ARP, runway, starting locations) a new walue that is higher by mentioned 1.76 m and ended up with aprons that are actually visible, but made themselves sort of a channel that lies, yes, you guessed it right, precisely 1.75 meters below the flattened terrain, but runway isn't wisible, since I didn't put anything below it and I'm 100% certain, that, if I put an apron below the runway, I'll get the same result as with aprons - visible surface burried into the ground.

And, Jon, as far as I can understand the situation, that "maybe" is not needed, since runways definitely don't produce flattens anymore.
Click to expand...


I'm using "sloped flattens" to remove those "channels"
around some airport boundries. Makes me wonder why
ACES went to the trouble of creating the "round
earth" model and didn't do anything to make
runways, aprons and taxiways conform to elevation
changes.
Alot of the airports I've been working with lately ( KTPH, KLSV, TNX and others ) sit on
"plateaus" created by the fixed elevation airport
backgrounds. Thus my need to use the sloped
flattens to blend those elevation changes
to remove the ugly ridges and trenches.
Now if only I could find an "easy to apply"
elevation conforming boundry fence...

Paul
 
You are missing a point here. The problem is that as far as the situation is at the moment, there is no way to modify stock airport elevation.
At least I can confirm this for rising it to a higher elevation, where all elements (with presence of a flatten to a higher altitude)will drill themselves into the ground to the elevation of stock airport value, completely disregarding altitude values from a new file.
 
You must log in or register to reply here.
Back
Top