Krishty’s Sim Forums

Head tracking for cockpit views will be in the next version, but a few details still need to be worked out. For example, how to use head tracking in external views and nose view …

No longer handled by plane code. Vibration, head bobbing, and other special effects are now handled in the core. Extensions merely provide a set of viewpoints to the core.

This also paves the way for head tracking.

Will be in the next version.

Seems like this exact issue is back.

The only change that comes to mind is: dynamic and static trails were rendered separately until a few weeks ago. When I fixed the contrail memory corruptions that rendered traffic unusable, I combined the rendering of both into one loop.

I chose this little place ( Agordat in Eritrea): it is on the edge between highlands, sand dunes, and rocky mountains; there are three airfields and several small towns nearby; a few airliners spawn in sight; If you fly along, you don’t fall off the edge of the map for at least 15 minutes. image.png...

Fix has landed.

Fix has landed.

Feature has landed.

Fixes have landed.

The repository has been force-pushed to a new version. git pull --rebase is required. F-22: Use Two Horizon Colors   TAW: Fix Moving Map Crash (rebased)   Fix Layout & Memory Leaks on Plane Controls Page (rebased)   Fix Keyboard Navigation on Plane Controls Page; Fix Focus After Message Box (reb...

Not delete it completely, but switch off the code for the next release. It doesn’t work right, it cannot be selected, it shouldn’t be in the executable.

Interesting version. Here is the version string from the EXE: version $Revision: 3.23.2.35 $ by Derek on Nov 18 1996

DID,DAT format is standard, but the name hashing is unlike EF2000 v2.

I identified three problems: Somewhere in the plane control settings, focus gets lost.   If you open the version info dialog (or if the extension error dialog opens during startup) and you press Esc to close, focus to the main window will be gone. You have to click or Alt - Tab back to it.   Plane s...

I downgrade this from critical to nice to have. First, I doubt that leaving the terrain is a major use case. Second, the fix becomes more complicated as it performs pretty bad when applied to all coordinates; it performs better but becomes pretty complicated when applied only to the viewer.

I found that sometimes, the control configuration dialog will look like this:


There is a memory leak which, in addition to the graphical artifacts, makes the dialog slower with each invocation.

Will be fixed in the next version.

Wait … if you swap out the texture, doesn’t this mean that markings on enemy planes are replaced, too?

Will be fixed in the next version.

Will be in the next version.

som747.3 from TAW (as extracted by you in 2011) has the correct size; 3View starts at a distance of 25 units like with all other 747 versions.


So this is a bug in TAW 2.0. Closing this bug report for TFXplorer.

Okay you tipped me in the right direction; it gets more complicated. I took som747.3 from the ADF file set we extracted last year and it’s good . Now I look at som747.3 from TAW 2.0 and it’s bad  – wrong scaling factor, just like you showed above. Now on to vanilla TAW to see if the error was introd...

Now that you mention it: From what I remember, TAW has 4 or 5 tiles with extra textures for randomization, but those textures are all the same, resulting in a net zero effect. TAW2.30 has 5 sea tiles, so that would be better for checking.. Could this have to do with the moving map? The moving map is...