|
Post by Kyzrati on Jan 21, 2013 2:13:39 GMT -5
If your game crashes for some reason, or you find some other general problem that doesn't relate directly to some data file or other content for which there is already another thread, write about it in here and we'll see about getting it fixed.
If applicable (error/crash), be sure to attach a copy of run.log to your post, and a description of what you were doing / was happening at the time of the error. Even better would be an inclusion of steps to repeat the problem, if it's not already obvious.
|
|
|
Post by 10101 on Jan 22, 2013 1:37:51 GMT -5
I think that could get a general problem, so i'll put it here. Was the result of a Fire Elemental burning down all and everything. Seems the roof of a hut was turned into rubble falling down on a chest. (and no 2 props at the same cell) PS: could also have been the tavern burning. Attachments:
|
|
|
Post by Kyzrati on Jan 22, 2013 9:09:03 GMT -5
Damn, I was hoping to not see anything in this thread for a while  Massive collapse of buildings with contents I've tested before, but maybe I've since changed something that could cause that error. It has to do with the rubble from the upper floor not being placed properly (yes, no overlapping props allowed, and apparently in this case the rubble wasn't displaced properly). Should be easy enough to test again: I get to burn down a bunch of buildings!
|
|
|
Post by Kyzrati on Jan 23, 2013 8:04:28 GMT -5
This turned out to be an example of the precise thing I was hoping to find by opening the game up to heavy modding and dynamic content through sa.xt. Turns out this fatal error was caused by old displacement code that assumed if it destroyed an object, that space would be empty afterward. Enter special abilities, which can be used to spontaneously create new objects when one is destroyed, as with chests, so the engine was destroying an object (the original chest) before trying to place rubble at that location, but the chest was spawning another prop before the placement actually took place.
Thanks for reporting this one. Took me a bit to figure out because the old code had always worked fine, but now I know I need to go back and check that objects destroyed are actually leaving empty spaces when they're assumed to be...
EDIT: Just released 8.5, which fixes this issue (and a new version of Rookie's Tale to take advantage of the change).
|
|
|
Post by 10101 on Jan 25, 2013 18:16:12 GMT -5
Hate to say it, but seems i found a new one. Problem is, that i can't say, what happened. I tested a little Garrison i created, and suddently i got this error. All i can do is post the logfile and hope it is of any help. Attachments:
|
|
|
Post by Kyzrati on Jan 25, 2013 20:02:52 GMT -5
Were you using the new Dijkstra path area view? And were you using it immediately at the beginning of the game before doing anything else? (This gave the error as you started up?)
That's all I can think of for this, since pathfinding has never had any problems before but this error seems to be the game trying to find a way to face from a point where z=1 to another with z=5, which isn't even in the map and seems quite odd.
Depending on your answers maybe I'll need to try and load up your file myself to find out what's really causing it.
|
|
|
Post by 10101 on Jan 26, 2013 3:34:41 GMT -5
I don't even know, what that Dijkstra is. I was only working around the Garrison trying to get to the entrance in one piece. (Those Crossbowmen seem to do a good job). It happened during the enemy movement. I can post the files, but i'm not sure if you'll be able to easily repeat that error.
|
|
|
Post by Kyzrati on Jan 26, 2013 5:27:56 GMT -5
Ah, by Dijkstra I was referring to the new feature in R8.5: press ctrl-p twice to see the entire area your unit can move to.
If it happened during the enemy turn then that's not it. You've found a genuine error here, but the only way to solve it would be for me to run the mission here, since I've never seen this and it could be part of your map design that's making it more likely--perhaps running it on auto would work if enemies are doing their normal thing?
|
|
|
Post by 10101 on Jan 26, 2013 6:57:25 GMT -5
I updated to 8.5 but got the same error again so here is the 8.5 mod. It's best to load the game i saved, because there i seem to get the error everytime after round 1 or 2 and i made the garrison spawn not very often as it's a 3x3 and therefore uses a lot of space.
All u have to do is to walk along that road.
|
|
|
Post by 10101 on Jan 26, 2013 6:58:41 GMT -5
... And if i would at least think a bit, i would've added the file. Attachments:
|
|
|
Post by Kyzrati on Jan 26, 2013 8:08:56 GMT -5
Found it. Took about 1 minute... You have an error in your script! See line 115 of cataclysm_spawning.xt: your commander is allowed to wander outside the map. Partially my fault because I never even checked that coordinates are within map bounds, but I'm trying to do as little as possible on this eventually-to-be-replaced system.
Nice garrison by the way! Check F2 of your NE section though; looks like it's missing a bit of roof there.
|
|
|
Post by 10101 on Jan 26, 2013 9:18:49 GMT -5
Such a silly mistake.
The hole in that roof should be there for the smoke from the hearth to escape the kitchen.
|
|
|
Post by Kyzrati on Jan 26, 2013 9:39:13 GMT -5
Ah, yeah, I didn't see what was under there, guessed it might have been a hearth but remembered seeing 'h' and thought they might be chairs.
|
|
|
Post by Aves Dominari on Feb 14, 2013 18:01:58 GMT -5
I was playing ARRP for a while (a thousand aliens is quite a few of them), and I realized that none of the grenades were working when I tried to bring a sectopod down with a brick of HE. Alien grenades, normal grenades, HE... proxy greandes work, but none of the other ones do.
|
|
|
Post by Kyzrati on Feb 14, 2013 19:48:22 GMT -5
Um, perhaps you forgot to prime them first?
|
|