| Category | Farming Simulator 19 |
| Created | 08.12.2020 10:11 |
| Yngve Bæsj (Yngve90) | 08.12.2020 10:11 |
|---|---|
| I test my map after almost every change I do, and for some strange reason the map suddenly fail to load. I go to test it as usual and while loading the map and pressing Enter to spawn in, the loading screen is stuck there (game isn't freezing). The only change I did before this happened was sculpting some terrain, removed some foliage, painted gravel and for the first time added MountainRock01bend.i3D to my map. The last one is even removed now, and the LUA issues remain. The log states alot of LUE errors, for instance: 2020-12-08 09:57 Error: Parse error in 'C:/Users/Yngve/Documents/My Games/FarmingSimulator2019/mods/NyFosnes/maps/map.i3d' at line 9352. not well-formed (invalid token). 2020-12-08 09:57 Error: failed to load map C:/Users/Yngve/Documents/My Games/FarmingSimulator2019/mods/NyFosnes/maps/map.i3d 2020-12-08 09:57 Error: Running LUA method 'loadMapFinished'. 2020-12-08 09:57 dataS/scripts/gui/base/MapOverlayGenerator.lua(118) : bad argument #1 to 'ipairs' (table expected, got nil) Further down the log: 2020-12-08 09:57 DensityMapModifier: invalid entity id 0. 2020-12-08 09:57 DensityMapModifier: called from dataS/scripts/fieldJobs/FieldManager.lua (57) 2020-12-08 09:57 DensityMapModifier: invalid entity id 0. 2020-12-08 09:57 DensityMapModifier: called from dataS/scripts/fieldJobs/FieldManager.lua (58) 2020-12-08 09:57 Error: Running LUA method 'update'. 2020-12-08 09:57 dataS/scripts/fieldJobs/FieldManager.lua(65) : attempt to index local 'ids' (a nil value) And then a buttload of LUA call stacks I haven't seen in my log before. e.g: 2020-12-08 09:57 LUA call stack: 2020-12-08 09:57 dataS/scripts/terrainDeformation/TerrainDeformation.lua (39) : createTerrainDeformation 2020-12-08 09:57 dataS/scripts/placeables/Placeable.lua (1180) : new 2020-12-08 09:57 dataS/scripts/placeables/Placeable.lua (804) : createDeformationObject 2020-12-08 09:57 dataS/scripts/placeables/SiloPlaceable.lua (134) : finalizePlacement 2020-12-08 09:57 dataS/scripts/placeables/Placeable.lua (976) : finalizePlacement 2020-12-08 09:57 dataS/scripts/placeables/SiloPlaceable.lua (286) : loadFromXMLFile 2020-12-08 09:57 dataS/scripts/missions/mission00.lua (671) : loadFromXMLFile 2020-12-08 09:57 dataS/scripts/misc/AsyncManager.lua (42) : lambda 2020-12-08 09:57 dataS/scripts/misc/AsyncManager.lua (119) : runLambda 2020-12-08 09:57 dataS/scripts/misc/DeferredLoadingManager.lua (39) : runTopTask 2020-12-08 09:57 dataS/scripts/main.lua (1904) : update 2020-12-08 09:57 Warning (script): Unknown entity id 0 in method 'addTerrainDeformationArea'. Warnings i get in the last part of the call stacks is things like this: Warning (script): Unknown entity id 0 in method 'setTerrainDeformationOutsideAreaConstraints'. Warning (script): Unknown entity id 0 in method 'setTerrainDeformationBlockedAreaMaxDisplacement'. Warning (script): Unknown entity id 0 in method 'setTerrainDeformationDynamicObjectCollisionMask'. Warning (script): Unknown entity id 0 in method 'setTerrainDeformationDynamicObjectMaxDisplacement'. Warning (script): Unknown entity id 0 in method 'writeTerrainDeformationBlockedAreas'. 2020-12-08 09:57 Warning (script): 'createTerrainDeformation': Argument 1 has wrong type. Expected: Int. Actual: Nil 2020-12-08 09:57 ..\..\..\src\base\scripting\lua\LuaScriptSystem.cpp (882): expectedType == Value::VoidType || expectedType == Value::ClassType Error: Running LUA method 'update'. and so forth.. Bear with me- I don't know much about LUA-related things, and I don't know what any of this means.. |
|
| Yngve Bæsj (Yngve90) | 08.12.2020 10:19 |
|---|---|
| Alright so... I fixed it... Don't know how or why but I got it working again after deleting a renamed transform group that contained 2 other renamed transform groups. I even removed some foliage that could be under the sculped terrain, but that didn't work. So again- what apparently fixed this was deleting a transform group that branched to 2 other empty transform groups.. I HIGHLY doubt that this was the real issue here. Can anyone explain this..? |
|
| Bilbo Beutlin (BBeutlin) | 08.12.2020 14:47 |
|---|---|
| That can happen if the label of the transform contains illegal characters. For labels and filenames use plain ASCII chars only (A-Z, a-z, 1-0 and underscore '_' instead space). |
|
Note: Log in to post. Create a new account here.