Apple Silicon: network, No server found

[Jamie]

Oh my God, I can't believe that you finally managed it. I can't wait to return home to try it.

After the connection are you closing the other Jar running in workaround 1 or it must stay open?
 

Once PSX is connected to the server, you can close the other app. If you need a static small JAR app, I use this: Dienstplan converter. It converts Lufhansa systems Netline Crew rosters into iCal format. Not useful for PSX, but it's very small and I keep this running in the background

@Hardy: I don't know why or what is happening, the weird thing is when I script all the workarounds in a bash or zsh: it doesn't work either. This blows my mind   Gives me the same errors as if I only start PSX by clicking the start.jar. Some weird sandbox/silicon/MacOS interfering with networking credentials, no idea.
For me no big deal, the workaround works just fine for me.

[Hardy Heinlin]

To everyone interested, just for reference:


You can start AerowinxStart.jar like this:

java -jar AerowinxStart.jar Captain.pref

See Aerowinx Operations Manual page 94 for more details.


You can start Aerowinx.jar like this:

java -Xmx500m -Djava.library.path=Interfaces -jar Aerowinx.jar

This is the command that AerowinxStart.jar executes; it reserves a memory of 500 mb, and links to the USB and audio interfaces. These features are necessary. That's why starting Aerowinx.jar directly without these parameters will not load PSX.

[Jamie]

You can start Aerowinx.jar like this:

java -Xmx500m -Djava.library.path=Interfaces -jar Aerowinx.jar

This is the command that AerowinxStart.jar executes; it reserves a memory of 500 mb, and links to the USB and audio interfaces. These features are necessary. That's why starting Aerowinx.jar directly without these parameters will not load PSX.

Extremely helpful Hardy! Thank you so much! I made an Aerowinx.app (has Contents folder and 1 script) and as soon as I started this with your command line options I finally got the much needed MacOS security popup:

I clicked Allow of course and voila! Now PSX is connecting without a hitch! Nice

If I switch off the Java access (wasn't there before!) It stops PSX from connecting to a server


Great success!

[Hardy Heinlin]

Good trick :-)

This might also be the solution to get sound (or better frame rates) on non-Intel Java versions, as I think the sound problem (or frame rate problem) is actually a security problem.

[Jamie]

Not sure if the Licencing allows this Hardy, in the background its nothing more than putting stuff in a subdirectory.

I call this the 3rd workaround, which is my preferred right now Thanks to Hardy for pointing me into the right direction.

What I did is I created a 'real' MacOS app bundle, that seems to trigger the MacOS Sequoia 15.x to open the right ports.
Some Mac basics: an App is nothing more than a special directory with the extension .app. Now in Finder if you right click on an App you can view its contents (Show package contents). From there on you can browse trough the Apps contents (or directories).

Long story short: I created my own Aerowinx.app which contains the script to start PSX + the whole Aerowinx directory all in 1 Aerowinx.app. This gives me peace of mind and this also triggers MacOS Sequoia 15.x to open up the network ports for Java. If you want to try this yourself, here's a little tutorial.

* as always backup your originals first *

- open Finder
- go to Applications
- create a new directory called Aerowinx.app -> Add the .app extension, click Add
- right click Aerowinx > Show package contents
- create a directory called Contents and open this directory
- create a directory called PSX (or your choice, but the script further-on calls PSX)
  copy all your Aerowinx files to this PSX directory so that PSX/Aerowinx.jar exists.
- in Aerowinx.app/Contents/ you need to create a file also called Aerowinx no extension!
  The easiest way to do this is to open Terminal (Applications/ Utilities)
  - cd /Applications/Aerowinx.app/Contents
  - nano Aerowinx
  - paste the following:

Code Select Expand

#!/bin/sh
cd "$(dirname "$0")"/PSX
java -Xmx500m -Djava.library.path=Interfaces -jar Aerowinx.jar  - ctrl-x -> yes -> confirm the filename again <enter>


The structure should look like this:

Code Select Expand

Applications/
  Aerowinx.app - Contents
                 \_ Aerowinx (this is the script file without extension)
               - PSX
                 \_ your Aerowinx files like the Jars and all subdirs
If all works well, you will be able to start the App from the Finder/ Applications/ Aerowinx.

You can add a fancy icon (google howto), search the forum for the icons, and of you go!
I tested this Aerowinx.app on my Mac mini and there it works as well: got the security popup and all works fine now.

Pro tip: you can add all sorts of stuff using an Info.plist xml, haven't really looked into that.

[Jamie]

Good trick :-)

This might also be the solution to get sound (or better frame rates) on non-Intel Java versions, as I think the sound problem (or frame rate problem) is actually a security problem.

Maybe, I do not get better frame rates with the ARM64 edition btw? Now I need some fresh air first Will try the ARM version later today.

[PanosI]

Finally PSX in MacBookAir : A main client !

The easiest way to start through the terminal.

[Jamie]

Maybe that's why I never had problems. I have always launched from the command-line.

This makes sense, as apparently Terminal.app has always had full local network permission. I see people use the Terminal.app to start older MacOS programs which do not trigger the Local Network permissions popup.
I'm not sure if this is an Arm/Silicon issue, rather a MacOS Sequoia thing. The new security settings panes (e.g. Local Network) need to be triggered by the App itself. There is no way to add Apps manually to allow them to access the Local Network.

I see if I can create a simple MacOS app which triggers 'java' to be added to the MacOS security settings. This would solve the Silicon/Sequoia network problem with Aerowinx PSX as well.

[Jamie]

Finally PSX in MacBookAir : A main client !

The easiest way to start through the terminal.

Happy for you that it works!!!

[PanosI]

Happy for you that it works!!!

Thanks !

I noticed that if I close the terminal window or the other jar running eventually the connection stops.

[Jamie]

I noticed that if I close the terminal window or the other jar running eventually the connection stops.

Yeah, you need to keep the other app running. It's not that a big deal is it? I'm looking into getting this "Java" forced into "Settings > Privacy & Security > Local Network". Then you don't need any further workarounds.

[PanosI]

Yeah, you need to keep the other app running. It's not that a big deal is it? I'm looking into getting this "Java" forced into "Settings > Privacy & Security > Local Network". Then you don't need any further workarounds.

Of course it's not a big deal. Just mention it. So happy to have the MacBookAir as client.

[Jamie]

Of course it's not a big deal. Just mention it. So happy to have the MacBookAir as client.

Yeah sorry, I didn't mean it that harsh Could you send me the location where your Aerowinx.jar resides? Maybe on your Desktop in a folder? I would like to test something.

[PanosI]

Yeah sorry, I didn't mean it that harsh Could you send me the location where your Aerowinx.jar resides? Maybe on your Desktop in a folder? I would like to test something.

Applications\PSX_10\Aerowinx

[MFarhadi]

This might also be the solution to get sound (or better frame rates) on non-Intel Java versions, as I think the sound problem (or frame rate problem) is actually a security problem.

I did try this method, but still unable to use ARM64 Java to run PSX with sound enabled.

[Jamie]

Applications\PSX_10\Aerowinx

I presume its the Applications folder in your root? Like /Applications?

I prepared an App for you: only contains 1 file, the script to start PSX. If PSX starts, try to connect to a server. Sequoia will popup with the question to allow Java to access your local network. This adds 'java' to the Local Network permissions. From now on PSX works by starting the AerowinxStart.jar just like on every other pc/os and you can Bin this Aerowinx app.
Get the file here (unzip in /Applications) -> Aerowinx.zip

The script, nothing fancy:

Code Select Expand

#!/bin/sh
cd /Applications/PSX_10/Aerowinx
java -Xmx500m -Djava.library.path=Interfaces -jar Aerowinx.jar


[PanosI]

I presume its the Applications folder in your root? Like /Applications?

I prepared an App for you: only contains 1 file, the script to start PSX. If PSX starts, try to connect to a server. Sequoia will popup with the question to allow Java to access your local network. This adds 'java' to the Local Network permissions. From now on PSX works by starting the AerowinxStart.jar just like on every other pc/os and you can Bin this Aerowinx app.
Get the file here (unzip in /Applications) -> Aerowinx.zip

The script, nothing fancy:

Code Select Expand

#!/bin/sh
cd /Applications/PSX_10/Aerowinx
java -Xmx500m -Djava.library.path=Interfaces -jar Aerowinx.jar


Yes it's in the root, the default location. I am not very familiar with MacOs.

Many thanks, Jamie. I'll try it in the afternoon at home.

[PanosI]

There is no solution.

The computer (Mac) Gods are not with us Jamie.

https://aerowinx.com/board/index.php/topic,5643.msg61406.html#msg61406

https://aerowinx.com/board/index.php/topic,7576.0.html

I presume its the Applications folder in your root? Like /Applications?

I prepared an App for you: only contains 1 file, the script to start PSX. If PSX starts, try to connect to a server. Sequoia will popup with the question to allow Java to access your local network. This adds 'java' to the Local Network permissions. From now on PSX works by starting the AerowinxStart.jar just like on every other pc/os and you can Bin this Aerowinx app.
Get the file here (unzip in /Applications) -> Aerowinx.zip

The script, nothing fancy:

Code Select Expand

#!/bin/sh
cd /Applications/PSX_10/Aerowinx
java -Xmx500m -Djava.library.path=Interfaces -jar Aerowinx.jar


Success !

I quoted also myself for the contrast ;-) 

No terminals, no commands just the plain old shortcut on my desktop and we have MacBook Air as "A main client".

Thank you very much and all this thanks to your persistence.

I hope all the friends in the above threads who were tormented with this problem find this thread and the solution.

[Jamie]

Success !

Great success! So we can confirm that this is a MacOS Sequoia problem and not per se a Mac Silicon issue? Thanks for testing PanosI, now I need to find a way to push this 'java' exception in the Local Network permissions Basically a Java JAR file which does some local network stuff would be sufficient. I could bundle this into this .App and call it "Java Local Network enabler" something like that.

I hope all the friends in the above threads who were tormented with this problem find this thread and the solution.

I don't really have an overview of who all are experiencing or have experienced this issue; most users are probably still flying on Windows. Of course, more Mac users will show up in the future. I'm curious to see how the new macOS Tahoe will behave. Does it still include Rosetta? I am an Apple Apps Beta Developer, but I don't quite dare to make the switch yet.

Edit: Rosetta 2 will be phased out in MacOS 27. I'll stay on Sequoia for the time being anyway. Have iOS26 installed and I don't like the UI changes.
They're ugly

Edit2: Workaround in 2027 will be a Parallels VM with either light-weight windows or macOS Sequoia.

Anyway thanks Hardy for the AerowinxStart.jar bypass, that helped a lot.

[FlyItLikeYouStoleIt]

Edit2: Workaround in 2027 will be a Parallels VM with either light-weight windows or macOS Sequoia.

It is awful under Parallels.

If/when Rosetta2 is truly deprecated there will be four other solutions:

(1) Run PSX without Audio under a native ARM Java
(2) Stop upgrading MacOS and stick with a version that has Rosetta2
(3) Buy a cheap x86 Windows or Linux laptop
(4) Hardy recodes PSX to move from LWJGL2 (no ARM support) to LWJGL3 (ARM supported)

EDIT: to my limited understanding such a rewrite is far from trivial as LWJGL2 provided a lot of helpers for USB and audio; LWJGL3 entails switching from JInput to libusb, and having to manage raw openal bindings or finding new libraries to do the same.