I am having an issue with how the dedi handles multiple profiles on the same VM instance. Perhaps what I am doing is not supported, but looking at this if I didn't have both sets of ports forwarded for both dedi's this could result in connection issues when I change between profiles. This is 100% reproducible. Win7 VM, 2 VCPu, 3GB RAM Profile #1: player Multiplayer.ini settings: Simulation Port="54297" HTTP Server Port="64297" Profile #2: player2 Multiplayer.ini settings: Simulation Port="54298" HTTP Server Port="64298" Desktop Shortcut: C:/Program Files/rFactor2/Core/rFactor2 Dedicated.exe Start in: C:/Program Files/rFactor2/ - Launch Shortcut - Dedi screen comes up with "player" profile already selected - Load Track: - 54297 TCP LISTENING - 54297 UDP * - 64297 TCP LISTENING - Exit, all ports release - Launch Shortcut - Dedi screen comes up with "player" profile already selected - Change to "player2" - Load Track: - 54297 TCP LISTENING - 54297 UDP * - 64298 TCP LISTENING - Exit, all ports release - Launch Shortcut - Dedi screen comes up with "player2" profile already selected - Load Track: - 54298 TCP LISTENING - 54298 UDP * - 64298 TCP LISTENING - Exit, all ports release As you can see when I switched from one profile to another the new dedi instance did not use the TCP settings from the new profile but instead retained the settings from the profile that was active when I opened the window. What this is doing is blocking me from running two dedi's at once since after I start up one and re-open the next window that second instance is trying to bind to the first instances TCP. I keep getting "Ensure multicast ports not in use.." or whatever the message is. What is odd is I had both running at one point, but I'm not sure the extra recipe I did. I'll keep trying, but for now I can reproduce the above unexpected behavior 100% of the time (10 tries used to make this post). I was having the error when trying to start both in build 300. I continue to have the issue in 342 but update wasn't working so I just installed 342 over 300. I may try a fresh install, but the behavior was definitely in 300. Any help and/or confirmation of what I am seeing would be appreciated.
I should mention how i made the second profile, because perhaps that has some impact. - player profile exists - copy player profile folder calling new folder player2 - rename player.PLR to player2.PLR - edit multiplayer.ini changing Simulation Port and HTTP Server Port Not sure if there is something else I should be doing, but dedi isn't throwing any errors and lets me switch between profiles. So sorry for the multi-edits on the first post, it's late and my eyes were playing tricks on me flipping between profiles.
It is 100% mandatory that you launch muti servers with the +profile command line option. The profile selector in the GUI doesn't work correctly. The dev team is aware of this bug. Has something to do with the port checking coming before it actually changes the profile. So for server one the command line should include this: +profile "player" And server two: +profile "player2" Also, make sure the working directory on your shortcut points to the root folder of your rf2 install (one level up from the core folder where the exe is located). While you are playing with shortcuts, check out the +oneclick option too. It will start a server minimized without asking any questions. Just add that option once you get it setup the way you like it.
