f16jockey_2

It says to look for an updated version of Fsuipc so see if you can find one made for the open beta of fsx-se (...)

The Fsx-se you use, version 10.0.63003.0 of fsx-se, is the open Beta version (...) An open beta version is a version that is unfinished. Put out there so users can help find the issues and report them back to dovetail.

The FSX-SE Open Beta was made by Microsoft, not Dovetail.

It seems to add some improvements, but is mainly equipped with telemetry tools for marketing (and guiding the development of) the upcoming new MS Flight Simulator. This is clearly, almost literally, written in the Open Beta description on Steam.

When it has done it's purpose of gathering data from users, it will most likely vanish in thin air (this is not written in their description, but just what I suspect).

I doubt Mr. Dowson will make an upgraded version of FSUIPC for this.

But of course, I can be wrong.

Wim

INSTALLATION FOR FSX-SE:

SetupPath="C:\Program Files (x86)\Steam\steamapps\common\FSX"

Checking version of the FSX-SE EXE:

... Version 10.0.63003.0 (Need at least 10.0.62607.0)

!! WARNING !! This version of FSX-SE is later than any known by this FSUIPC4.

There may be problems. Please check for a later version of FSUIPC4!

Better ask this at the FSUIPC Forum

https://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/

Wim

I don't understand this.

If you've correctly installed SDK for FSX-SE and it's working, you should only rewrite the paths in your boxed FSX dll.xml to

C:\Steam\steamapps\common\FSX\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll (the Steam path).

No need to install the SDK a second time. How did you manage that btw?

Both versions can work with that one single SDK imo.

[ADDED] IF your boxed FSX is FSX+Accel

Wim

Is this the user's aircraft, an AI aircraft?

Doesn't look default to me, guessing from the shadow, so what aircraft?

Download link?

Wim

Sometimes the newest (actual) FSXscenery.cfg is located in the ProgramData folder.

+/-1

ALWAYS in ProgramData, from W7 (maybe already Vista, dunno) and up.

The Users\etc... location was only used (and still valid) in XP.

@OP: I'm also confused about the "remote", but SCENERY.CFG errors at startup in most (if not all) cases mean you've deleted scenery folders before properly disabling/deleting them in the simulator's Scenery Config Menu.

I once had an external disc going disconnected (flawing connection), with a tsunami of scenery errors just like your's as a result. Just a thought...

Wim

... with the autobrake not deploying, it deploys on touchdown but stops working 3 seconds later ...

When I read "deploying", I think you rather mean the spoilers, not the autobreak? Or not?

What's the 767 addon btw?

Wim

That's good.

Just an idea: if you move those contactpoints a bit apart laterally you'd get two separate touch-down tire smokes as well?

Wim

It not simple.

IMO one needs to know the actual gear animation's full compression and full extension values.

That's all written into the model. If you don't have the model itself, it's all trial and error.

Anyway, I used following document for a simple C140 model I'm making myself (a 5 year project I'm afraid :o), and I found it to be quite useful.

http://www.mudpond.org/contact_points.pdf

Maybe it helps in understanding the relations between the different parameters.

Wim

For W7 the active scenery.cfg is located

C:\ProgramData\Microsoft\FSX\SCENERY.CFG

But as Loyd says, don’t do anything stupid like deleting without a backup.

Wim

Your version is outdated, the latest for FSX is 4.974.

Try updating and see what gives.

http://home2.btconnect.com/petedowson/

Wim

B767 - Check

Total fuel loss - Check

Gliding to nearest airport - Check

It’s quite obvious which RW incident you’re recreating.

But unfortunately I don’t have a solution.

Remember that back in ‘83, Air Canada 143 had some friction gain due to the collapsed nose gear.

No idea how to simulate that.

Wim

It appears that many people got excited and skipped over the "Beta" part of the title. This is not a final release and bugs should be expected.

+1 on the "skipped the beta part", but...

from what I read, I see no plans for a "final" release.

It's above all meant as a telemetry object for a marketing study for the upcoming MSFS 2020 release.

We've released a new beta branch for FSX:SE that will help us gain valuable new telemetry data that will help us in the development of the new Microsoft Flight Simulator. If you are interested in assisting us with this process, please follow the link below, select the branch labeled fsx-beta – External Beta and select “yes” when asked if you allow telemetry. Remember that you are always able to opt out of the beta branch and return to the normal branch at any time.

IMO there's a chance it remains a beta until it has done it's purpose, to dissolve in thin air after that.

Wim

And your download accepted "TDS" as a valid manufacturer?

Why not? Carenado products (as only one example) have the annoying "feature" of putting themselves as manufacturer.

It's just a text string, remember? No checking WSE.

Wim

20?? - whatever year it is released, Latest MS Version should be FS11.0 / FSXI

IIRC FS9 was never used until after FSX/FS10 came out, neither were the other "number" version names.

A rose by any other name would smell as sweet, some obscure English playwright once wrote.

Wim

Yes, but FSXX would read as FS1010, FSXX/XX - FS20/20 or FSMMXX - FS2020. Maybe 2020 hindsight is why MS are getting back into Flight Sim.

You forgot FSXI (FS11).

FSXX reads as FS20 btw, I studied Latin for 6 boring years.

Wim

Verzonden vanaf mijn iPad met Tapatalk

In your fsx.cfg check your setting for TEXTURE_MAX_LOAD in the [Graphics] section and set it to 4096.

Never do this on a low-to-middle-end system, it makes things even worse.

Wim

What is FSXX?

Not interested in the new sim until it's actually there, but I must confess: FSXX isn't a bad acronym.

Wim

It seems as if there is an actually a problem, perhaps with a flightplan, and not with a specific aircraft...

I've searched on "ntdll.dll error" (which Jorgen identified) in combination with "AI Traffic".

Guess what? It actually IS one single aircraft with a corrupted texture that can cause (iow already has caused) this error.

You have identified a quick and easy error recreation flight (Edinburgh 07:57am). Think you need to start there, and bring in your AI flightplans one by one, until you get the crash... Once you've identified the AI flightplan, another elimination process for the faulty aircraft is at hand.

Wim

To be honest I don't know why you are using the Project Opensky Airbus A330 in FSX when there is the Thomas Ruth A330 series which has native FSX models, panel & a good VC. Do a search in the library for toma332b.zip, toma333b-1.zip & toma3mrt.zip.

+1

Wim

It can be solved by adding a line zorder=nn (nn being a number) to specific [WindowXX] sections of panel.cfg, thus defining which sections should be topmost.

Can’t remember the details right now, not at my simputer.

An example (download location) of some panels giving trouble would be helpful.

Wim

In fact the OP is right.

It's not clear from the download page nor the readme within the download which model to use.

@OP: the actual model matching info is found on this page (made by aerofoto :)):

http://tonymadgehjg.proboards.com/thread/6297/vl-hjg-b727-texture-inventory

Scroll down to below "HJG B727-200 SERIES TEXTURE/BASE PACK/MODEL CONFIGURATION" to get your info (about halfway the page).

And while I was there, I could as well copy/paste the info you've asked for:

Korean Air 1995 = VHF model / B727-200 EARLY NTL/VHF JT8D-7 base pack

All Nippon Airways 1990 = VHF model / B727-200 ADV NTL/VHF JT8D-17 base pack

Wim

Your link doesn't point directly to the download.

Down the page from his link he said.

Yr link points to only one of the three packages (for FSX/P3D) on that page.

I tried one of them as well, works OK.

Wim

But I still have trees in the apron lol.

The ORBX Global airports are in the folder shown below (not retyping that! lol).

It also contains a _CVX.BGL file, which is a common name for a landclass update for that local airport.

In theory it should remove the trees.

Did you move this folder's priority above UTX as well?

If you already did this, I'm lost as well. Sorry.

Wim

FSX (and also FSX-SE in suppose) keeps a copy of a "virgin" scenery.cfg in the main FSX program folder.

I would copy/paste this file into C:\ProgramData\Microsoft\FSX (or whatever it's called in Steam) and see what gives. When doing this, you will need to add yr addons to the Scenery Library again, but I think it's less drastic than a complete reinstall.

Wim

ui_manufacturer=Boeing

ui_type=737-MAX8 BRITISH AIRWAYS

ui_variation=BRITISH AIRWAYS

The purpose of this post in relation to your original question is unclear.

Just wanna say that with these entries, the title on yr selection screen will read

”Boeing 737-MAX8 BRITISH AIRWAYS BRITISH AIRWAYS”.

No big deal, but for me that would be a no-go :cool:.

Wim