News:

Precision Simulator update 10.181 (1 February 2025) is now available.
Navburo update 13 (23 November 2022) is now available.
NG FMC and More is released.

Main Menu

Recent posts

#91
Hangar 7 / Re: PSX/Java not starting anym...
Last post by Jeroen Hoppenbrouwers - Tue, 10 Jun 2025 07:06
No no no  :-)   Put a big label on all other screens:   DID YOU START THE INSTRUCTOR STATION?     :-)


Joking aside, these big rig sims need check lists and procedures very much like a real airplane. Not for the pilots but for the engineers running the sim.
And after working on one for a few years you also learn that you need to treat construction and modification like a real airplane ...
#92
Hangar 7 / Re: PSX/Java not starting anym...
Last post by renquetfrederic - Tue, 10 Jun 2025 06:34
yep, will put a big label on the screen: START THIS ONE FIRST ;) ;) ;)
#93
Hangar 7 / Re: PSX/Java not starting anym...
Last post by Jeroen Hoppenbrouwers - Tue, 10 Jun 2025 06:18
Yet another thing to check!

And no, you're not the first one to suffer from this issue ... folder sharing is a known trick that comes back to bite you at a certain moment.


Hoppie
#94
Hangar 7 / Re: PSX/Java not starting anym...
Last post by renquetfrederic - Tue, 10 Jun 2025 06:05
hey hoppie,

I came across the same issue this week, after a week of not operating the sim, but this time on another pc. then a lightening bolt stroke me: my instructor pc wasn't running (in both cases).

So what happened: a while ago, I installed symlink on my aerowinx.jar (on all pc's). they are linked to a shared folder on my instructor pc (the only one with a keyboard and mouse). So, if my instructor pc isn't started up first, the shared folder is not available, ergo: aerowinx.jar is not available. So, PSX will not start automatically as the pc thinks the file is missing.

If the instructor pc is started first, all works fine!!

kind regards,

Frederic
#95
Accessories / Re: CPFLIGHT MCP AUTO CONNECT
Last post by renquetfrederic - Tue, 10 Jun 2025 05:58
hey all,

for now, i have it up and running using a "mini mouse macro" and a batch file. the batch file starts the MCP connector first and after a second, the mini mouse macro "clicks" on connect. so far it works perfectly.

@ alex : I believe this is only to connect to PSX automatically on start up. the user interaction is to open the comm port to which the mcp is connected to the pc.

@ JG : I am looking to do the same with the msfs, still not yet there, but the idea to start a new thread when i achieved it, is added to the to do list
#96
Hangar 7 / Re: Worldflight 2024
Last post by Jeroen Hoppenbrouwers - Mon, 9 Jun 2025 06:07
(just information in case it happens again)

If you connect a SIM router over the long and winding internet road, it is possible that the internet link freezes up due to a (temporary) line issue somewhere. Many TCP routers will start buffering the PSX output but eventually the outbound buffer will fill up and the router will stop accepting new input. This is good, as TCP is a reliable byte stream, you cannot just drop bytes out of the middle.

When the outbound TCP link blocks, the PSX server will have to stop right there -- for the same reason, that TCP cannot just start dropping bytes.

This is not a local PSX server or router problem, but obviously it is not desired. The only good option is to break the outbound link and allow PSX to keep pushing bytes out to the Router. Some PSX Routers may have this safety valve already.

So take care, the OUTBOUND link is as important to be smooth as the INBOUND link.


Hoppie
#97
Hangar 7 / Re: Worldflight 2024
Last post by Kurt - Sun, 8 Jun 2025 18:27
Quote from: macroflight on Fri,  6 Jun 2025 07:14Socat is a very simple TCP relay, originally from the Unix/Linux world. I used a Windows version I found on https://github.com/firejox/WinSocat. Install: "dotnet tool install -g winsocat" in a PowerShell window. Run: "winsocat TCP-LISTEN:10747,fork TCP:123.123.123.123:10747" in a PowerShell window (I think it needs to be started as administrator) on the computer that runs your main PSX instance. Replace 123.123.123.123 with the IP address of the remote "master sim" in the shared setup.

In theory, any TCP relay should work if you don't like winsocat for some reason. If you run your main PSX instance on macOS or Linux you should be able to use the regular socat.

What it does: for each new TCP connection made to port 10747 on the relay, it starts a new TCP connection to port 10747 on the remote sim and then forwards the data between the sims in a transparent way.

This worked surprisingly well - Macro and I tested out this afternoon and after messing around getting winsocat to work locally on my main PSX sim PC it was "just" a matter of changing main PSX server to client and point it to localhost - BAM - just worked with all addons and all my PSX instances without any issues so far.

Thanks Macroflight for helping out - looking forward to try some shared cockpit sessions so we can have all wrinkles ironed out well before WF2025 :D

Cheers
#98
Accessories / Re: PSX.NET.MSFS2024.WASM - MS...
Last post by Bluestar - Sun, 8 Jun 2025 02:56
Quote from: macroflight on Wed,  4 Jun 2025 21:41Gary unfortunately is very busy with his day job right now, but he gave me permission to share the VATSIM altitude fix (for the problems between the transition level/altitude and 18000ft) that I helped him to test a while back.

Before this update, the "altitude bodge" was applied when over 18000 feet. But as it turned out, the cutoff altitude should have been the TA/TL instead.


I just did MMGL to MMSM and was 350 feet low once I descended below to TL.  The TL for Mexico is FL185.  There was no ATC and the nearest aircraft was a couple hundred miles away.

#99
Accessories / Re: My 747 seen in two places ...
Last post by Gary Oliver - Fri, 6 Jun 2025 12:42
I'll send this thread over to Ross Carlson and see if he has any ideas.
#100
Accessories / Re: My 747 seen in two places ...
Last post by macroflight - Fri, 6 Jun 2025 11:43
This has now happened again. Departed Sydney, and after a while people started talking about a 747 that was still on the runway.

One pilot messaged me and asked me to reconnect. He had used the .aircraft command in vPilot to identify that it was my aircraft that was still on the runway. ATC (and VatSpy/VATSIM Radar) could see me in the correct location, just as last time.

After reconnecting, my plane was no longer stuck on the runway as seen by other pilots, but it was instead stuck in the position/altitude that PSX/MSFS2024 was when I reconnected to VATSIM.

I then tried restarting vPilot, but by then I was outside the 100nm range of ".aircraft", so I do not know if a vPilot restart helped. You can't see your own aircraft using that command.

Gary's comment that vPilot sends two data packets (one for other sims and one for ATC) was helpful. I will try to dump the network traffic when this happens again.

Apart from that: any suggestions on what information I should try to collect when it happens again? Any secret debug options to vPilot?