SOLVED Can't join my dedicated Server over LAN

[redapg]

I have a Problem.

The Solution, that works for me now, is in THIS Post.

Spoiler: old Post

I had to make a fresh Windows 10 Install, due to a SSD Crash.
Today i did install the Steam Command dedicated Server and tried to join it with a LAN Shortcut, like i always did it in the last Years.

But it doesn't work anymore and i have no Idea why.

The old/working Method was:
- i did start the dedicated Server, before i did start Steam
- then i started Steam/rF2 with a Shortcut, with the Entry
"F:\Steam\steamapps\common\rFactor 2\Launcher\Launch rFactor.exe" +multiplayer +connect="127.0.0.1:64297"
in the Target: Field of the Shortcut.

That always did work.
But now, the Game opens, but the dedicated Server Window gets closed.
And no Matter, if i point to the Launch rFactor.exe or directly to the rFactor2.exe, the dedicated Server Window gets closed.

Does anybody have an Idea, what the Reason can be?

 

[8Ball]

When you work it out, if you get the time, please do a concise up to date tutorial a Billy goat could understand.

 

[redapg]

When you work it out, if you get the time, please do a concise up to date tutorial a Billy goat could understand.

Unfortunately i currently have no more Ideas, where to look at.
That is the first Time ever that it is happening (for me).

 

[redapg]

After some Tests, it figured out, that i can start the Steam dedicated AFTER Steam and rFactor 2 are started already.
That did never work in the Past.
BTW Game and dedicated Server are on the same PC.
But i can not get it shown up in the in Game Server List with LAN checked.
Does anybody know what is necessary to get the Server being shown there?

Joining by Shortcut does not work, because rFactor 2 is running already, so my only Option is, to join it from the Server Lobby in Game.

 

[redapg]

OK.. seems as if i get it running again.
I will make some more Tests to be sure, but it looks good so far.
Detailed Information will follow soon.

 

[Woodee]

Always best to start the dedi before Steam and rF2... because if the dedi crashes then rF2 doesn't need restarted to get it going again. Is it just you joining the LAN server?

 

[redapg]

It's really a strange one.....
But i have the Suspicion, that it is more Steam or Windows 10 related.
It's a fresh Windows 10 Home, Steam, rFactor2 and Steam Command dedicated Server Installation.
The Values in the player and Multiplayer JSON Files are default (e.g. "HTTP Server Port":64297,)

I will not describe here, how the Steam Command dedicated Server has to be set up.

This is how i got it working for me again:

At first, create a Shortcut to the ..\rFactor 2\Bin64\rFactor2.exe and put it to a Place wherever you want (you, of course, can also rename it to Start rFactor 2 LAN for Example).
Rightclick on it, select Properties and then Enter into the Field Target:
"F:\Steam\steamapps\common\rFactor 2\Bin64\rFactor2.exe" +multiplayer +connect=127.0.0.1:64297
and into the Field Execute in:
"F:\Steam\steamapps\common\rFactor 2
The bold Parts have to be replaced with your Path and if you use another Port, it has to be replaced too.

Start Steam
Start rFactor 2
Start the Steam Command dedicated Server
It now should look like this in the Taskmanager:

Close rFactor 2
Doubleclick on the new created Shortcut to the rFactor2.exe
That's it.
You normally should directly join the Screen with the Option to race or to spectate and then the normal Car Selection.....

That is how it works for me now.
But because we talk about Windows, Steam and rFactor 2, there is no Guarantee, that it works for everybody else too.

 

[redapg]

Always best to start the dedi before Steam and rF2... because if the dedi crashes then rF2 doesn't need restarted to get it going again. Is it just you joining the LAN server?

As described in my opening Post, that doesn't work for me anymore.