VisualPSX suite 6.4 and 7.4, build 5668 released

[Garry Richards]

Hi all,

This update fixes bugs in processing runways with displaced landing thresholds and in the timely selection of the correct runway offset when airborne.

If you have experienced problems with landing offsets or if you have stopped using them I recommend that you try this version with full offsets enabled.

Happy flying!

[cagarini]

Thx Garry!

[pcpilot]

Hi Garry,

The download link for the latest release does not work for me.

Thanks for all your efforts producing VisualPSX.

Graham.

[Garry Richards]

Hi Graham,

Try refreshing your browser when you have the download page open.

Cheers,

[pcpilot]

Hi Garry

Just downloaded the file from a work PC with no problem :-).

Must be an issue with my home setup, despite different browsers and a reload it would not download last night.

Thanks for your swift response.

Graham.

[G-CIVA]

Gary,

Many thanks for your continued support.

Working like a dream here

 

[Frans Spruit]

Hi Garry,

Working like a charm, many thanks and keep well,

cheers,

Frans

[Kabbers]

Hi Garry, an immense thank you from me today - very happy days here thanks to you gift of sharing VisualPSX with us, cheers Garry

[airbusguy320]

I am sorry to say that with the latest build of VisualPSX and aerowinx PSX 10.0.5, I continuously have crashes of FSX. I did not have this problem with previous versions.
FSX freezes and VisualPSX keeps trying to contact FSX.
Anyone else has the same problem?

[tango4]

Hi Garry,
And thanks again for your efforts.
Sorry I did not post before, I just did not have time to use PSX in the past weeks.

Unfortunately, on this latest release, RunwaysPSX does not find my FSX SE, and so I can't run it.

Just for info, version 7.4 does detect my p3Dv2 install, I just have the issue with 6.4.
I only have FSX SE and P3dV2 on this computer, not FSX regular or P3dV1 for info.

Sorry, it seems I really am a pain in the .....

If you have an idea what could be wrong, that would be nice, otherwise, don't sweat it.

Anyway, really nice of  you to try and solve everything.

All the best

Charles

[Greg Hateley]

Hi Gary,
Thanks for your great software, working well with p3Dv2.5.
While on Vatsim we noticed that there is discrepancy between the PSX altitude and what Vatsim is receiving. After checking P3D, there is a 500foot missmatch between PSX and P3D at altitude. eg. PSX 35,600 with p3D showing 36,100.
Any thoughts this? Is there something I am doing wrong in the settings?

Best Regards
Greg

[Garry Richards]

@ Airbusguy320: Have you been able to resolve the problem? It seems that no-one else has encountered it. If not can you provide more detailed information, such as whether this happened at startup or after PSX had connected.


@ Charles: Looks like FSX-SE has yet another set of registry keys. Do you know how to search the registry using Regedit? If so look for HKEY_LOCAL_MACHINE\\SOFTWARE\\DovetailGames and let me know the names of the sub-keys below that. RunwaysPSX looks for the sub-key FSX but yours might be FSX-SE or something else.


@ Greg: VisualPSX sends the true altitude of PSX TO FSX/P3D. When flying above the transition altitude you would normally set the QNH in PSX to STD (1013 hPa or 29.92 in). It's altimeter will then show the pressure height which will be higher than the true altitude if the actual QNH is lower than 1013 hPa or lower than the true altitude if the QNH is higher.

So a flight level of 350 could be higher or lower than 35,000 ft, but all aircraft flying at that flight level would be higher or lower by the same amount. The atmospheric pressure decreases by 1 hPa for every 30 feet increase in altitude so if the QNH was 1030 hPa the difference between true altitude and pressure height would be about 500 ft. I'm guessing that's what the case was for that flight.

Cheers,

[ScudRunner]

Ref Greg's comments I have also noticed this when flying on Vatsim.

E.G The area QNH was 1032mb, I was cruising at FL380 with STD set and the controller pointed out my indicated altitude on his system was  FL385. There were a number of other aircraft in the area at similar flight levels to me that did not get this comment so I assume I was the only one!

After a bit of thought I came to the same conclusion that Garry has outlined above.

I don't do any controlling on VATSIM so not sure if the controller systems display true altitude for all aircraft or whether or not some of the FSX-only clients actually send pressure altitude through. I would have thought they must use pressure altitude.

Will follow up on another forum and advise.

chrs
Scud.

[cagarini]

@ Greg: VisualPSX sends the true altitude of PSX TO FSX/P3D. When flying above the transition altitude you would normally set the QNH in PSX to STD (1013 hPa or 29.92 in). It's altimeter will then show the pressure height which will be higher than the true altitude if the actual QNH is lower than 1013 hPa or lower than the true altitude if the QNH is higher.

So a flight level of 350 could be higher or lower than 35,000 ft, but all aircraft flying at that flight level would be higher or lower by the same amount. The atmospheric pressure decreases by 1 hPa for every 30 feet increase in altitude so if the QNH was 1030 hPa the difference between true altitude and pressure height would be about 500 ft. I'm guessing that's what the case was for that flight.

Cheers,

Just to add that there is yet another factor that could account for it - geopotential height variation with density due to temperature, modeled in PSX but not in FSX, P3D or XP10, even when using the most sophisticated weather injectors.

Of course, while it affects all aircraft in the same area and airmass by the same amount, aircraft flying in FSX / P3D can actually have a true altitude / height that is different from PSX, where that effect is taken into account...

The "from high to low watch out bellow" in PSX also works for the temp side of that sentence...

[Hardy Heinlin]

When flying with an online ATC system that doesn't model OAT dependent altitude errors, you should deselect the checkbox for this effect on Instructor > Situation > Aerodynamics. See tooltip text for details.

However, there is no effect in the upper airspace. When clicking the checkbox while you're at FL350, you will see no difference.

This is relevant for low altitudes only.


Regards,

|-|ardy


To demo the effect, try:

03 Approach 024 - Trondheim - Cold day.situ

[tango4]

@ Charles: Looks like FSX-SE has yet another set of registry keys. Do you know how to search the registry using Regedit? If so look for HKEY_LOCAL_MACHINESOFTWAREDovetailGames and let me know the names of the sub-keys below that. RunwaysPSX looks for the sub-key FSX but yours might be FSX-SE or something else.
Cheers,

Hi Garry, I don't have a DovetailGames key directly in HKEY_LOCAL_MACHINE\\SOFTWARE\\DovetailGames.

I have keys under:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\DovetailGames\\FSX
I have 3 keys:
*(Default)         Value not set
*exe_path        D:\\SteamApps\\steamapps\\common\\FSX\\fsx.exe
*install_path    D:\\SteamApps\\steamapps\\common\\FSX\\

I can't find another reference to dovetail in my registry.
Perhaps my install is corrupt somehow ?

Charles

[Garry Richards]

Thanks Charles. The Wow6432Node is a windows version difference. I will add it to the search paths in the next update.

Cheers,

[tango4]

Once again thanks A LOT for all your time.

Charles

[Greg Hateley]

Ref Greg's comments I have also noticed this when flying on Vatsim.

E.G The area QNH was 1032mb, I was cruising at FL380 with STD set and the controller pointed out my indicated altitude on his system was  FL385. There were a number of other aircraft in the area at similar flight levels to me that did not get this comment so I assume I was the only one!

After a bit of thought I came to the same conclusion that Garry has outlined above.

I don't do any controlling on VATSIM so not sure if the controller systems display true altitude for all aircraft or whether or not some of the FSX-only clients actually send pressure altitude through. I would have thought they must use pressure altitude.

Will follow up on another forum and advise.

chrs
Scud.

Speaking to an Vatsim ATC controller last night, I was told that what is set on the PSX PFD is what Vatsim controllers should see. Eg, At Flight Level 360, 36,000 feet STD on the PFD is what Vatsim should see. This is where I noticed the other night that we were told that we were not at the correct altitude.
Cheers
Greg

[airbusguy320]

It happens all the time now. It is probable that it is a FSX problem, but it is strange.
The memory and processor usage are not at maximum, I get a "bing" sound, FSX freezes and VisualPSX is unable to contact FSX.
I took a screenshot of it but I don't know how to add it here.