VisualPSX Suite upgrade to versions 6.6, 7.6 and 8.6, build 5821 released

[Garry Richards]

Hi Peter,

Glad the VisualPSX Suite is doing it for you!

Cheers,

[speedbird965]

It's great!!! 

Thank you and cheers, Peter

Hi Peter,

Glad the VisualPSX Suite is doing it for you!

Cheers,

[cavaricooper]

Garry-

Occasionally (not all the time, but frequently) I lose my P3D visuals as soon as I start VisualPSX (v7.6).  Then, as soon as I select BEACON in my pre-start flow, the view returns... has anyone else reported seeing this?  Not a showstopper, but I thought I ought to mention it.... in case others were seeing the same.

Loving every minute of VisualPSX & TrafficPSX- you moved my goal-posts, thanks a million!

Best- C

[GodAtum]

I do have a few minor issues. On starting, VisualPSX puts my plane in P3D is below ground. But when I cycle the taxi light is fixes itself.

Also, the weather inject from PSX to P3D crashed P3D.

And lastly, there was a wierd issue when I was flying from KFJK - RJAA. on approach I noticed that in P3D I was miles off the coast, but in PSX I was right ontop of the airport. After restarting visualPSX, it put P3D in the right place.

Thanks for your continued development and I hope my testing helps 

[asboyd]

I have been using VisualPSX Suite (Traffic and Visuals) for some time with P3D V2.5 and since I have been using the default FSX 747 I have not had a problem. What I had to do though was save my cold and dark situ with the correct long and lat to place me at the gate correctly. I always start my flights at FlyTampas YSSY and Gate 32.... I figured that is the one I have jumped on the plane to Europe via Singapore so I would use it.

I do have a small problem where I will be following an A380 along the taxi way to R34L, and then P3D loads terrain data and the A380 and all other traffic disappear for several minutes. By the time the A380 reappears it has taken off and is heading away from me.

As I have only seen this a couple of times and did not see it as a serious issue, I did not worry about it.
Cheers,
AlexB

[Garry Richards]

Hi Carl, Chris and Alex,

These are intriguing behaviours that prompted me to check the P3D SDKs in case I had overlooked any changed SimConnect usage.

There weren't any that are relevant to VisualPSX and that leads me to suspect interactions with other addons. I suggest you try running VisualPSX with no other addons to see if that eliminates the problems. If we can identify one or more that result in VisualPSX behaving strangely we might be able to work out how to make our addons work well together.

That's my best guess at the moment.

Cheers,

[cavaricooper]

Garry-

Wilco. Ta!

C

[asboyd]

Hi Garry,
Currently I am only running VisualPSX and TrafficPSX.
I have not been firing up my hardware interfaces (PSXseecon) due to reorganisation of my flight sim).
So the traffic problem is with only the two above turned on.

Cheers,
ASB

[cavaricooper]

Garry:

Done! 

Started P3d and then PSX on the server ONLY.  Started VisualPSX (on a second machine).  As soon as P3d reloaded, I saw some red sparks ahead of the nose and then the visuals faded out.  Actuating the BEACON switch resulted in all being right with the world.  Turning the BEACON off resulted in a fade out to black.

I think there is an issue with airport/AFCAD height involved, as there was some "settling" of the aircraft (which resulted in a heavy nose drop animation in P3d?).  There is probably a difference between PSX and FlyTampa's airport height at TKPK but I am at a loss as to how to examine each database.

HTH

Best- C

[Garry Richards]

Hi Alex,

How was the taxying A380 generated - online with VATSIM, real traffic passing through PSX, real traffic fed directly into P3D, P3D AI traffic or something else?

[Garry Richards]

Hi Carl,

I agree with you. The P3D aircraft is probably being held below the surface by VisualPSX. If you switch to an external view you may see its tail sticking up above the ground.

This suggests that RunwaysPSX is not using your addon scenery data, but is using the standard airport data. Confirm that the FlyTampa airport is listed in the P3D scenery library above the standard airport and that the FlyTampa entry is marked as active, with the standard one being inactive.

Then run RunwaysPSX again and replace the old .vpx file in the VisualPSX folder with the newly generated one. VisualPSX should then use the FlyTampa airport data instead of the standard data for that airport.

[Gary Oliver]

C,

I had the same problem...

Turn off 'G Effects' in the realism settings. It causes the fade to black issue.

Cheers
G

[cavaricooper]

Garry R-

I'm fairly meticulous with my scenery.cfg- yes the pay ware is the active one. I keep RunwayPSX updated. I did happe to look outside.... Allest gut.

Gary O-

Will give that a try and report back.... I wonder what the correlation is? Can't fathom....

C,

I had the same problem...

Turn off 'G Effects' in the realism settings. It causes the fade to black issue.

Cheers
G

Best- C

[asboyd]

I am using Full Terrain (Orbx) AI Traffic, that is then passed by TrafficPSX to PSX.
If I am not using trafficPSX then the AI traffic appears to be OK, but it has only happened a few times (less than 5 so far). The TCARS still shows all AI traffic though!!!!!

Cheers,
asb

[Gary Oliver]

Will give that a try and report back.... I wonder what the correlation is? Can't fathom....

The G force on the aircraft in P3D makes it think the pilot is blacking out and fades the screen to black :-)

[cavaricooper]

Ok... But why does it stay black, and what does the Beacon switch have to do will alleviating g-force effects? Speed jeans, yes... But Beacon?



I'LL BE DARNED- DISABLING G-EFFECTS IN P3D REMOVES THE FADE TO BLACK.... ta!

C

[cavaricooper]

Garry:

Something else I noted after 7.6 was that I get 2 choices for P3d, x32 and x64.  What is this referring to?  AFAIK P3d remains 32 bit....?



I habitually run RunwaysPSX on the SIM computer, and then copy the resulting file (Runways_PSX_v71.vpx) in that computer's VisualPSX directory to the SUPPORT computer VisualPSX directory, where VisualPSX and TrafficPSX run.  The VisualPSX folder on the SIM computer functions mostly as a repository for this file's construction (and as a backup folder).  Is something amiss with the v7.1 named output despite the latest v7.6 VisualPSX build?

Thoughts?

Ta!

C

[G-CIVA]

If you see both a _32 and _64 entry in RunwaysPSX choose the one that matches your CPU, either 32 or 64 bit.

[cavaricooper]

RTFM and SEARCH- I should have!

Ta!

C

[Garry Richards]

I'LL BE DARNED- DISABLING G-EFFECTS IN P3D REMOVES THE FADE TO BLACK.... ta!

This is probably due to a bug in P3D. Lockheed Martin have developed the product considerably with a lot of new programmable features, especially for military mission simulations. The actual G Force variables have been present since FSX days and are not used by VisualPSX which is why I suspect a bug in P3D.

Is something amiss with the v7.1 named output despite the latest v7.6 VisualPSX build?

No. The difference is so that users are not obliged to run RunwaysPSX whenever there is an update  to any of the programs. I always mention in the ReadMe file for new releases whether RunwaysPSX needs to be run.

There are now three versions of each application which differ only in the version of SimConnect with which they were compiled. The code for each version is identical except for the name of the scenery generator they work with. In all there are now nine applications emanating from three sets of source code (VisualPSX, TrafficPSX and Runways PSX).

So if I fix a bug in one version of VisualPSX it will be automatically fixed in the others as well. To keep everything in sync and easy for users and myself to keep track of, I update the application versions of all nine in each release. The release notes show what changes, if any, have been made to each application.

Cheers,