farming-simulator.org Tutorials for FS22

[Snake Man]

PMC Farming aka Farming Simulator 22 - https://www.farming-simulator.org/

Our FS22 Map making tutorials page.

Anything you wanted to know about creating and editing terrains, making small medium or big maps, this is the place to be.

If you see any errors even typos on the website, please let us know here in PMC Tactical forums and they will be corrected.

[jdunn1019]

past down a few error i figure out and you can add to the website.....

og file C:/Users/jdunn/Desktop/TestRunner_public_0_8_0/TestRunner.log
10:43:40 INFO TestRunner - Checking for update
10:43:40 INFO TestRunner - Loading predefined testSuite and output path
10:43:40 INFO Config - required TestRunner Config Version: 3
10:43:40 INFO Config - Config.test_data_path: C:/Users/jdunn/Desktop/TestRunner_public_0_8_0/FS22_4xBlankMap
10:43:40 INFO Config - no game installation directory given in testSuite, searching installation locations
10:43:40 INFO Config - retrieved game installation path 'C:/Program Files (x86)/Farming Simulator 2022' (v=1.0.0)
10:43:40 INFO Config - Config.game_path: C:/Program Files (x86)/Farming Simulator 2022
10:43:40 INFO Config - config.output_dir: C:/Users/jdunn/Desktop/TestRunner_public_0_8_0
10:43:40 INFO FileCollector - Collected 3175 files for 16 extensions
10:43:40 CRITICAL root - XML parse error in C:\Users\jdunn\Desktop\TestRunner_public_0_8_0\FS22_4xBlankMap\maps\mapUS\placeables.xml
not well-formed (invalid token): line 28, column 35
aborting test run due to setting stopTestOnParseError=true
10:43:40 ERROR root - XML parse error in C:\Users\jdunn\Desktop\TestRunner_public_0_8_0\FS22_4xBlankMap\maps\mapUS\placeables.xml
not well-formed (invalid token): line 28, column 35
aborting test run due to setting stopTestOnParseError=true
Traceback (most recent call last):
File "dataCollectors\XMLCollector.py", line 35, in collect
File "xml\etree\ElementTree.py", line 1222, in parse
File "xml\etree\ElementTree.py", line 580, in parse
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 28, column 35
[10:44 AM]
The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "TestRunner.py", line 311, in main
File "TestRunner.py", line 135, in perform_test
File "TestRunner.py", line 158, in _collect_data
File "dataCollectors\XMLCollector.py", line 41, in collect
TestRunnerException.TestRunnerException: XML parse error in C:\Users\jdunn\Desktop\TestRunner_public_0_8_0\FS22_4xBlankMap\maps\mapUS\placeables.xml
not well-formed (invalid token): line 28, column 35
aborting test run due to setting stopTestOnParseError=true
Press any key to continue . . .

this is when i run the Lastest TestRunner 0.8.7 version

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
another error Common error people will get after 1.8.2

Error: Failed to register console command 'gsTrafficSystemToggleDebug. Command was already registered!

This error is from the Trafficsystem in the GE ... soo first u need to make a tranform group and add all the spline in one group, in the user add follow user atti

the error come up when you dont have those Attributes in the splines and every spline must have them




I hope this help people i nornall not a person to post on a forum @snakeman please edit my post to make senses if you don't understand it thanks ...

[Snake Man]

Good info, thanks! I'll take a look at those and write them into our web page.

[Snake Man]

Thanks jdunn1019, your above post has been linked in FS22 common errors page.

Also FS22 DensityMapHeightUpdater error topic was linked there.

[jdunn1019]

Awsome...

[Snake Man]

There was link typo in Farming Simulator 22 (FS22) HOWTO Create 45km Terrain Tutorial, got it fixed.

It unfortunate that howto create 45km terrain for FS22 page has been up since 2022 and only now, TWO years later I spotted that broken link bug, nobody has notified me about it. BTW it was a random chance that I spotted that bug in apache web server error log, just perfect timing to happen to see it.