Jump to content

f16jockey_2

Registered Users
  • Posts

    1,429
  • Joined

  • Days Won

    1

f16jockey_2 last won the day on April 3 2023

f16jockey_2 had the most liked content!

1 Follower

About f16jockey_2

  • Birthday 02/26/1963

Personal Information

  • Location
    Belgium
  • Occupation
    Construction Engineer/CAD Operator

Simulators

  • Sims Used
    FSX
    DCS

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

f16jockey_2's Achievements

Community Expert

Community Expert (6/7)

  • Dedicated Rare
  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter Rare

Recent Badges

28

Reputation

  1. 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" Correct .. except for the problem we're trying to solve here. It's better explained in this thread (2nd post). Wim
  2. 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
  3. 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
  4. 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. Probably needless to say F9 and F12 should be freed from any FSX assignment. Wim
  5. 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
  6. Based on Jorgen's remark: After doing that and starting FSX, do you see the "Generating scenery file indexes..." popup? Wim
  7. My apologies for asking such an obvious thing: did you check you sliders? Wim
  8. https://drawingdatabase.com/category/aircraft/ Wim
  9. No idea what it does... No, the paths are from my install, and won't work with you. But you can use it as a guide. Wim
  10. 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
  11. 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
  12. 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
  13. FSPainter? Always tought it was for AI only. Wim
  14. 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
  15. 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. Please be aware some (most?) Posky aircraft simply DON'T HAVE a VC. FSX is 32bit but runs fine on Windows 10 64bit. Wim
×
×
  • Create New...