VisualPSX suite upgrade to v 6.5 and 7.5 released

[cavaricooper]

Dan-

How do you then taxi to and from stand? I use VisualPSX mainly for the "full-flight experience" which it allows for brilliantly.

Best- C

[Britjet]

Thanks Dan, but as Carl says - that sounds like a fudge?
I will try it though...

Peter.

[Tigh]

Hi Carl,

It's detailed on page 14 of the VisualPSX manual. All it does is momentarily set an offset based on your location and then works as normal, that's how Garry has designed it. However, as mentioned the runway detection can be a bit hit and miss I find.

It's setting at the start of the flight the same parameters that you get at the end of one if you have offsets enabled.

Cheers,
Dan.

[cavaricooper]

Dan-

Ta!  I will try it, as well as the other option of NO offsets.... I can live with the "jump" for now... perhaps in a future update.....

Best- C

[Garry Richards]

Hi all,

I don't get much time to work on VisualPSX these days but I did try some takeoffs from a sloping runway and confirmed the jump at liftoff. I figured this must be due to a slight lag in synchronising the FSX and PSX ground elevations. So i wrote a nice little smoothing procedure to eliminate it. To my consternation it had no effect, leading me to revisit the complex, but fully debugged, offsetting code. And of course I found a bug! What's more, the bug could explain why the offsets do not work properly for some users or at some airports. I will include a fix in the next update.

Cheers,

[cavaricooper]

Garry!

Cheers mate!  Ta!

C

[brian747]

Many thanks in advance, Garry!

Your dedication is hugely appreciated.   

Cheers,

Brian

[cagarini]

That's great news Garry!

It happens I just re-visited FSX:SE, and it comes really handy

[Britjet]

Excellent!. Many thanks, Garry!

Peter

[KeepDiscovering]

Hi

I haven't used the PSX 747 since upgrading to Windows 10. Since then, I can seem to get Visual PSX or Simconnect to work.

I've just updated to the latest version, amended all the IP's as per the manual etc, but now I keep getting 'Attempt to connect through SimConnect has failed'.

Any ideas so I can get the 747 back in the skies?

Cheers

[cagarini]

Hi

I haven't used the PSX 747 since upgrading to Windows 10. Since then, I can seem to get Visual PSX or Simconnect to work.

I've just updated to the latest version, amended all the IP's as per the manual etc, but now I keep getting 'Attempt to connect through SimConnect has failed'.

Any ideas so I can get the 747 back in the skies?

Cheers

Make sure you ( from the manual, and probably lost with  the upgrade to win10...):

"Do you need to run vcredist_x86_2010_SP1.exe?
Run this if neither of Microsoft Visual C++ 2010 x86 Redistributable or Microsoft Visual C++
2010 x86 Runtime is installed on any computer that will run one or more of the VisualPSX Suite
applications.
To find out if either is installed, open the control panel and select "Add or Remove Programs" (in
XP) or "Programs and Features" (in Win7 or Win8)."

and...

"For version 7: Do you need to run dotNetFx45_Full_setup.exe?
Run this if Microsoft.NET Framework 4.5 is not installed on any computer that will run one or
more of the version 7 VisualPSX Suite applications.
To find out if it is installed, open the control panel and select "Programs and Features" in Win7 or
Win8.
For"

[martin]

Your dedication is hugely appreciated.   

+1

Cheers,
Martin
(desperately trying to catch up with Language 2.0)

[KeepDiscovering]

Hi

I haven't used the PSX 747 since upgrading to Windows 10. Since then, I can seem to get Visual PSX or Simconnect to work.

I've just updated to the latest version, amended all the IP's as per the manual etc, but now I keep getting 'Attempt to connect through SimConnect has failed'.

Any ideas so I can get the 747 back in the skies?

Cheers

Make sure you ( from the manual, and probably lost with  the upgrade to win10...):

"Do you need to run vcredist_x86_2010_SP1.exe?
Run this if neither of Microsoft Visual C++ 2010 x86 Redistributable or Microsoft Visual C++
2010 x86 Runtime is installed on any computer that will run one or more of the VisualPSX Suite
applications.
To find out if either is installed, open the control panel and select "Add or Remove Programs" (in
XP) or "Programs and Features" (in Win7 or Win8)."

and...

"For version 7: Do you need to run dotNetFx45_Full_setup.exe?
Run this if Microsoft.NET Framework 4.5 is not installed on any computer that will run one or
more of the version 7 VisualPSX Suite applications.
To find out if it is installed, open the control panel and select "Programs and Features" in Win7 or
Win8.
For"

Hi jcomm,

Both are installed so I'm still at a loss!

Sam

[Britjet]

I have P3D V3 and Win 10 and it works fine...

I think your problem is all about Simconnect..

Go into the P3D V3 "redist" folder and EXECUTE the Simconnect.msi that is in the FTX-RTM folder.
Go to the users/Appdata/"yourname"/Roaming/Lockheed Martin/Prepar3DV3 folder...

Open Simconnect.xml with a text editor such as Notepad.
Change the IP to the local IP of the PC running P3D eg 192.168.0.XX
Save Simconnect.xml

Copy Simconnect.dll from the VisualPSX 7.5 folder to the "modules" folder in P3D

See if it works..

It should show connected to Simconnect Ver 3..

HTH

Peter

[KeepDiscovering]

Hi Peter,

I tried a clean install and doing what you've just said to no avail.

'Attempt to connect to through SimConnect has failed'.

Cheers

Sam

[Michael Benson]

I've sorted him out... don't worry 

[GodAtum]

Just setting up ... I can connect TrafficPSX to vPilot but the comm freq do not change. I have selected "Sebd PSX comms to P3D" and restarted. But when I change freqs in PSX they do not change in vPilot.

Got it working .. PSX was not connected!

[cagarini]

Today, while trying to set VisualPSX to work with FSX:SE and with WordFlight, I set my local instance of PSX as a main Client, and Boost Server.

FSX:SE was running on that same PC, so, 127.0.0.1 was used both in simconnect.cfg and simconnect.xml, but in VisualPSX I had to define the Main server as the WorldFlight PSX server, and that, in good part, is probably what causes the timeouts and the constant reload that never get's into a stable state between FSX:SE and VisualPSX.

Why can't the local PSX main client act itself as the Main server for VisualPSX, main and Boost ? That way, VisualPSX would talk directly to the local instance of PSX ?

In fact the answer is evident... If we have a remote PC running as a Main Server ( the WorldFlight server in this case ), and a local main client, also configured as Boost server, it can't be a Server ( other than a Boost one ), since it is already a Client... So, I must infer that there are variables in the client part of PSX that can't be changed to get their effects over to the Main Server, or even aren't available in the Client at all ?

[Hardy Heinlin]

A main client cannot be the main server.

A boost server is not a main network instance.

[cagarini]

Yes, unless the application doesn't need to change anything in the main PSX instance.

I believe that if that's the case, then the application would be fine talking only to the Boost server on one of the Main clients ?