f16jockey_2

10 hours ago, f16jockey_2 said:

IIRC this is the first scenery where the "no ground shadows" trick doesn't work.

Because my memory failed: one has to uncheck "Aircraft ground shadows" (Settings -> Display -> Aircraft casts shadows on the ground).

At least I remembered "something with shadows" 

1 hour ago, jorgen.s.andersen said:

there are no problems using FS9 models in FSX

Correct .. except for the problem we're trying to solve here.

It's better explained in this thread (2nd post).

Wim

12 hours ago, jorgen.s.andersen said:

I would urge you to use AIFP to check that ALL are in FSX format, and to recompile if necessary.

That's unnecessary IMO, as the initial post includes pics with the titles of the AI aircraft in top right corner.

AI traffic is present (nothing wrong with the flight plans), but it's invisible.

IIRC this is the first scenery where the "no ground shadows" trick doesn't work.

A possible solution would be to replace the WoAI models (FS9) with genuine FSX AI models.

That's lots of labour just to make this scenery work.

And as this is not the only problem with the scenery, I'd dump it.

Wim

Known problem, not specific to the Steam Edition. 

The combination of certain older sceneries with the use of non-genuine FSX AI models makes this happen.

The easiest way to fix is to uncheck Ground scenery shadows (Settings -> Display -> Scenery).

Wim

34 minutes ago, Cas141 said:

So the question is, will my not new Trackir unit work with Trackir 5 software, in windows XP?

I have no idea. In this thread NaturalPoint states older cameras work with TrackIR 5.

No mention of Win XP though. The only way would be to try.

40 minutes ago, Cas141 said:

Do you have any other suggestions on this

Probably needless to say F9 and F12 should be freed from any FSX assignment.

Wim

6 hours ago, Cas141 said:

However, when mapping buttons I cannot get the mapping to work on the two keyboard buttons which are used by the Trackir. In my case F9 and F12.

IMO you're trying to stick to the F9 and F12 keystrokes, and you want your joystick to emulate F9 and F12.

That's not the way to go.

Choose the action in the green drop-down menu, then click the button in the red area. It'll prompt for a keystroke or joystick button.

Press the joystick button of your choice and you're done.

As you see in the blue area, there's no need to stick to F9 and F12.

Wim

3 hours ago, jorgen.s.andersen said:

Where is that one located?

Based on Jorgen's remark:

On 1/24/2024 at 6:46 PM, Ryubunao1478 said:

I installed a flight plan from AIG, tried to substitute the missing aircrafts, and compiled them to my scenery file.

After doing that and starting FSX, do you see the "Generating scenery file indexes..." popup?

Wim

19 hours ago, Ryubunao1478 said:

Once I start up FSX, there's no aircraft traffic whatsoever. I can't find cars and trucks in roads, but I found cargo ships in a nearby bay.

My apologies for asking such an obvious thing: did you check you sliders?

Wim

15 hours ago, gambit9m said:

Do you know of a template like the one in the video I can use?

https://drawingdatabase.com/category/aircraft/

Wim

40 minutes ago, gambit9m said:

If I used the attached utility would that fix it

No idea what it does...

41 minutes ago, gambit9m said:

or could I just copy what you posted?

No, the paths are from my install, and won't work with you. But you can use it as a guide.

Wim

40 minutes ago, gambit9m said:

Do you know what the latest version of blender the 1.0.20 Blender2P3D/FSX is compatible with for FSX?

From the Wiki page at FSDeveloper: "... it incorporates compatibility with the latest API for Blender version v3.x.x (has been tested with Blender LTS v3.3.x)."

Wim

An example of DLL.XML with only the SDK entries and FSUIPC.

Note that each entry starts with <Launch.Addon> and ends with </Launch.Addon>

<?xml version='1.0' encoding='Windows-1252'?>
<SimBase.Document Type="Launch" version="1,0">
    <Descr>Launch</Descr>
    <Filename>dll.xml</Filename>
    <Disabled>False</Disabled>
    <Launch.ManualLoad>False</Launch.ManualLoad>
    <Launch.Addon>
        <Name>Object Placement Tool</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>F:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Traffic Toolbox</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>F:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Visual Effects Tool</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>F:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>FSUIPC 4</Name>
        <Disabled>False</Disabled>
        <Path>Modules\FSUIPC4.dll</Path>
    </Launch.Addon>
</SimBase.Document>

Wim

This series is old, but the best I found

The model is very rudimental (as you see) and the Blender version is outdated by a decade,

But it explains all the basics. 

Be aware: a steep learning curve, and by times tricky as you'll have to "translate" it yourself to the latest version of Blender.

Wim

1 hour ago, Honus said:

the A350-900 by FSPainter/M. Yutaka

FSPainter? Always tought it was for AI only.

Wim

On the King Air it's present.

On the Baron they "left it out on purpose" (meaning they forgot it) in the VC, but there is one the 2D panel.

Also, it's possible to assign a key combo for "NAV/GPS toggle" (I think it's blank by default).

Wim

21 minutes ago, ritcheyl said:

I seem to remember years ago that you had to install a Microsoft .dll file in the main FSX directory to get the virtual cockpits to load.

You need MSVCR70.DLL in the FSX root for the PoSky 777 gauges.

It uses stock FS2004 gauges (as the 777 was an FS2004 stock aircraft). So you'll need these gauges as well.

This applies to the 777 ONLY, and to some gauges only. If nothing of the VC shows, as you seem to imply, this won't solve the problem.

21 minutes ago, ritcheyl said:

except the virtual cockpits aren't showing up

Please be aware some (most?) Posky aircraft simply DON'T HAVE a VC. 

21 minutes ago, ritcheyl said:

Also, how do you know if FSX is running 64 or 32 bit? My system is Windows 10 64 bit so I'm assuming I'm running 64.

FSX is 32bit but runs fine on Windows 10 64bit.

Wim

10 minutes ago, ritcheyl said:

Is there a .dll file or other utility I need to install to make the gauges show up in the VC?

No, unless the readme of the "several FS2004 aircraft that have been modified to work in FSX" states something else.

More info would help.

Wim

2 hours ago, worldsfair said:

can anyone offer some advice as to how I can fix it?

Scenery doesn't change by itself.

It would be nice to share what you've installed (or tried to install) lately, and how you've already tried to "fix it" before posting on this forum.

Wim 

Last step (I hope).

AI Traffic can be compiled in two formats, FS9 and FSX.

Problem: when the two are mixed, FS9-format takes control and blocks FSX-format traffic. Only FS9 format is shown.

So now you need to find FS9-formatted files, this can be done with AIFP.

Once the files are found, you can either delete them (this means losing the traffic from these files) or convert them to FSX-format (same menu, the line below).

Once converted, don't forget to delete the original FS9 BGLs.

If this doesn't solve the problem, I'm out of thoughts.

Wim

Hi again,

sorry for misjudging your experience.

First thing to check is if the aircraft are installed OK. 

Do so by adding a panel to the aircraft.

In the above folder, create a folder called panel. In that folder create a text file named panel.cfg.

The contents of the folder should be (you can copy/paste) :

[fltsim]
alias=.\SimObjects\Airplanes\B737_800\panel

Do the same with the other aircraft you've added.

When starting FSX, your AI planes should now be in the list of flyable aircraft.

You should be able to select them and you'll get a view of them on the start screen (check if the repaint lines up, check for black aircraft etc.).

Once an aircraft folder checks out OK, you can delete the panel folder. Otherwise you aircraft selection screen will become overwhelmed.

You can keep a copy of this panel folder on your desktop for future use (at least, that's what I do).

If this doesn't solve your problem, the second step is to check the aircraft titles.

Load your flight plan in AIFP, and check for any RED lines in the AIRCRAFT LIST.

To correct this, the title=... in aircraft.cfg should be identical to the name in quotes in the Aircraft_???.txt file.

Use copy/paste to correct this.

Recompile and check the result.

If this still doesn't solve the problem, post back.

Wim

5 hours ago, LordofGats said:

this is somewhat the first time I actually installed some AI instead of the WOAI really

Hi Mr. Terry 

If WOAI (with it's handy installer) is your only experience, you probably forgot to install the AI aircraft models and the corresponding repaints.

The models and repaints are listed in this thread https://retroai.proboards.com/post/29391

But I don't have the ambition to rewrite an "How to install AI traffic from scratch"-thread.

Everything is already said and should be available on the web. IMO the AIFP manual should be a good start.

But it will be overwhelming with a rather steep learning curve.

Wim

13 minutes ago, Jungleace said:

I loaded an aircraft and it is semi transparent.

I think you're overrating the capacity of your new rig. Try lowering some overall graphic and scenery settings.

Wim

20 hours ago, Honus said:

I've got FSUIPC 4 in a module folder in FSX Steam.

If you just copied the folder from yr old system, that won't work.

You need to run the FSUIPC installer, which autodetects where FSX (boxed or SE) resides IIRC.

Get your installer from http://www.fsuipc.com/   (you need v4.977).

BTW the Modules folder is an FS2004 leftover, FSX works through dll.xml and exe.xml. FSUIPC can be installed anywhere.

Wim

10 minutes ago, Honus said:

If I wanted to move that

Warning: Don’t use Windows to do this.

Steam has functions to create new libraries on other discs, and to move apps between them.

Use these functions to move FSX:SE.

Wim

2 hours ago, airernie said:

The files are still deep

Windows allows to create desktop shortcuts to folders.

Wim

1 hour ago, mrzippy said:

I'm betting it's still in the FSX/Settings/Scenery/Scenery Library.

+1

If you're feeling lucky, you can also edit SCENERY.CFG manually.

You need the one in C:\ProgramData\Microsoft\FSX, not the one in the FSX root.

Wim