my server room window wouldnt show any cars or tracks until i set it how Radar has it above...and now is working fine...im just going with whatever works atm lol
Then you have the same messed up installation I guess. I just did an update on our server and I had to change nothing whatsoever.
Running the Mod Manager directly inside the Core folder in earlier builds resulted in it installing to the Core folder instead of the Data Path.
Running the dedicated server from the Core folder directly means,
it cannot find Core\data.path, since the subfolder Core does not exist in there. Therefor one needs to tell it to use ".." (the parent directory, which is the rFactor 2 installation folder) as working directory by appending +path=.. to the command line,
only if one runs it from outside the Launcher (!), otherwise, since Core\data.path cannot be read, the program seemingly falls back to the current working directory, which is Core.
So, if you previously started the Mod Manager the same way, directly from Core, it installed into Core. Running the dedicated server resulted in it finding those wrong "Installed" and "Manifests" folders and thus was able to start and find the installed components.
Since that procedure was obviously not intended by ISI, this is not a bug.
If one wants to start those applications outside the Launcher, it is possible. One option is to use the parameter +path=.., i.e. by appending it to the command line in the startup shortcut one has created. Another one is to go to the rFactor 2 installation folder and run "Core\rFactor2 Dedicated.exe" from the command line (cmd.exe). This has the same effect, since one is in the main folder which is the working directory then. That can also be achieved by manipulating the startup shortcut:
View attachment 6495
Note that the started exe file contains "Core" in the path, whereas the marked line does not.
Long story short, I´d suggest whoever has this problem, make a really fresh reinstallation and keeps the above in mind.
Kind regards,
Marcus