Solitude 1967Tracks 1.3

[LuisB]

LuisB submitted a new resource:

Solitude 1967 - The Solitude racetrack is an 11.4086 km (7.0890 mi) race circuit in Stuttgart, Germany.

The Solitude racetrack is an 11.4086 km (7.0890 mi) race circuit on public roads used for motorsport in the Leonberg area, west of Stuttgart, Germany. It is named after Castle Solitude and until 1965 has hosted various...

Read more about this resource...

 

[LuisB]

LuisB updated Solitude 1967 with a new update entry:

Solitude 1967 v1.1

The track was optimized it should works better with Low Specifications PC's.

Read the rest of this update entry...

 

[LuisB]

LuisB updated Solitude 1967 with a new update entry:

Added Solitude 1965 no barriers around.

​

The update are 3 solitude tracks:

• Solitude 65 - no barriers and all AC_POBJECTS.
• Solitude 1967 with barriers around and all AC_POBJECTS (moving objects);
• Solitude Low - with barriers and AC_POBJECTS reduced.

So the only difference is that I made a version of 65 year with no barriers.
Enjoy it.

Read the rest of this update entry...

 

[WhataMack]

I installed the 1967 version of the track and it took about one minute to load. It looked like the "Miscellaneous" portion of the loading took the longest time.

I saw a "persistent haybale issue" where haybales in the track stay there for following laps, which is obviously going to be an issue during a multi-lap race. I saved that session as a replay and saw the error below when getting back to Content Manager. Then I loaded up the replay, took a screenshot of the persistent haybales, then tried to exit from the replay and my entire system hung. Not just AC, but everything including Task Manager. I had to restart my system. Really disappointing.

 

[LuisB]

The problem is that AC is limited to moving objects and haybales together with the cones are almost 400. You can go in Race Department and download the last version 1.3 which gives the option of solitude_low where the moving objects are less than 100. In any case just for a try reduce the replay time in CM to a minimum and see what happens.