On a host dedicated server, the mission will stop and give a waiting for host message, then disconnect. Only happens when you have the boat rack with a boat loaded on the rack in the mission.
Description
Details
- Severity
- Block
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Operating System Version
- MS Windows 11 Home 10.0.22000 Build 22000
- Category
- Dedicated Server
- I created a mission with just a player, "Land_Destroyer_01_Boat_Rack_01_F", and "B_Boat_Armed_01_minigun_f" loaded on to rack.
- Save, and export to Multiplayer.
- Upload to hosted dedicated server. (Nitrous Networks in my case)
- From the "role assignment" screen, select a slot, and press "OK".
- The game never gets to the briefing screen to cancel or continue.
- Gives a "Waiting for Host" message, and then disconnects.
I have tested numerous ways. I first noticed the issue when I put the boat rack on the USS Freedom. If you remove the boat from the rack, it works fine. Only when the boat rack with a boat loaded does the game hang.
I tested on the USS Liberty at the boat launch position as well. Same issue.
It only happens on a hosted dedicated server. I used TADST and created a server, with no issues.
Arma Version: 2.08.148892
Windows 11 Home 10.0.22000 Build 22000
Event Timeline
Also what is hosted dedicated server? There are 2 types of servers, player hosted, you can start it from main menu, in which case you are hosting server, or dedicated, which runs on its own on dedicated machine. Which is it?
Hey,
Here are the 2 missions I used to test.
It is a hosted server by Nitrous Networks. It is not a player hosted server.
I have the 2 missions uploaded on the server, and setup on a vote system if you want to test and see live. Let me know if you need anything else. I'll leave it up for 24 hours.
OT: I am getting reports that the server is restart every ~10 minutes. I'll look into that.
Connection Info 23.235.255.218:2302
I'd guess your server is 32bit and is just affected by the 32bit crashing that we had pre-hotfix.
So your issue should be gone by now.