Game crashes with error outside the ship - solved

[rleigh]

Hello,

I've just bought Primordia on Steam.  I'm running Windows 7 (64-bit) on an Intel core2 quad with 8 GiB RAM.  The error is:

Adventure Game Studio

An internal error has occurred.  Please note down the following information.
If the problem persists, post the details on the AGS Technical Forum. (ACI version 3.21.1115)

Error: Unable to render character 0 () because loop 1 does not exist in view 96

Triggered moving away from the generator close-up view, fiddling with the inventory items on the generator close-up view and also on the second screen outside the ship.  Hope the above is useful, but if I can provide any other information, please just ask.

This mainly appears to be triggered when on the close-up view of the generator, if I select an item from the inventory, and then click outside the inventory with the item selected, in order to use it on the generator.

Thanks all,
Roger

[V0rador]

I experienced exactly the same crash at the same place with the same error message using the same OS but I7 3770k cpu and geforce 670 gtx series.

Just to be clear, not a game blocker as I was able to continue the story once I rebooted

[Narcoleptic]

Same crash, same error!

just had another, only this time loop 2 instead of 1, otherwise identical error.

Win 7 64 bit

[eruvalar]

Me too.

Also Win 7, i5 750, GTX570,

Crash after using inventory in generator closeup then moving away. No close option, he just floats around under the generator view, then it crashes.

Way to play into my already considerable save-game paranoia. :-D

[Werewhiskey]

Also experienced the same crash, when I was trying to investigate the hose while still being in the close-up generator view. Only happened once, so far.

Win7 64-bit, i7, GTX 580

edit:
Not related to the above error, but since there is no bug report thread, thought I might as well add this:
It also seems like some close-up views don't properly close and stay open until you leave the screen. This does not happen every time, though.

So far this has happened on the close-up views of the bar in Metropol, as well as the floating junk in the Underworks.

[wormsbuh]

Had one similar:

An error has occurred. Please conctact the game author for support, as this is likely to be a scripting error and not a bug in AGS.
(ACI version 3.21.1115)

in "NewCommander.asc", line 2732
from "room4.asc", line 223

Error Caracter.Loop: invalid loop number for this view

playing via Steam, win7 x64, i7 930, GTS 250

really nice lookin game btw! keep it up oldshool point'n'clickers

[DaveGilbert]

We're on this! In the meantime, to avoid the bug, close the inventory window by using the "OK" button instead of clicking outside the window. You only need to do this when you're at a close-up, like the generator.

[rleigh]

Thanks for looking into this!  In the meantime, your advice worked well, and I was able to complete the game with no further crashes.

The only (slight) potential glitch I noticed was that on entering the courthouse screen, I was sometimes able to walk straight past 187th to the door and try the keycard (which was unresponsive), but on walking back down the steps, 187th would then prevent me on the second attempt.  Maybe it's supposed to be that way, but I assumed I shouldn't be able to reach the door at this point.


Thanks,
Roger

[rleigh]

Also, I just wanted to thank you all for the time and effort you've put into Primordia.  It was an excellent game, and I thoroughly enjoyed it.

[MervynGraham]

I played the game  from a direct download in order to do a game review for adventureclassicgaming and I found no glitches whatsoever in the game. There were no freeze-ups or crashes and the game ran smoothly.

I use an Intel i7 980 @ 3.33 GHz processor, Windows 7-64 bit and a NVIDIA GTX 570 graphics card.

Reading all the problems here that have been listed, I am wondering if the problem lies with Steam, as there is no problem with the game.

[MarkYohalem]

@ Mervyn: There were changes made to the game after the press review version that introduced certain crashes, including the day-one UI / close-up crash.  I think some of the issues are Steam-related, though.

@ rleigh: Thanks so much!  The 187th glitch is a known one, but damned if we've been able to pin it down.  Because it's not game-breaking, we haven't shot ourselves.  Yet.