-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom field generated - Course Generator unable to #348
Comments
Log upload was not successful, can you upload it again pls? |
Can you give me the file from that custom field? |
i messed up and tried renaming it as an xml file so ignore any xml references? the error in game occurred before the xml renaming. i tried driving and saving a new custom field to get the right header but i didn't get asked to save field on 5 different courses... so i don't know if i messed up my courseplay altogether at this point. |
I Had the same issue on the Frontier Map and also the base map for that Eastern European place—I can't think of the name. |
Version
8.0.0.5
Game Version
1.4.0.0
SP/MP
SP (Singleplayer)
What happened?
I believe I was successful in generating a new custom field using vehicle drive (hoping for that map draw feature soon!) to cover 3 existing and separate fields and was sure to not overlap course.
Turned on "Prefer Custom Fields" setting. When attempting to generate a course using the custom field and setting the field position within the custom field, error "Could not generate course. Please try other settings. See screenshot.
How can we reproduce this?
Vehicle drive - create custom field over multiple existing fields, ensure that the course does not overlap at all. Attempt to generate course.
What did you expect to happen?
Since the "prefer custom fields" setting was enabled and I created a field without any overlapping points, I expected the course generator to respect the custom field preference and generate a course through the custom field.
Attach your log.txt!
Uploading log.txt…
Screenshots
The text was updated successfully, but these errors were encountered: