Monday, October 5, 2009

The glory of Raven Shield / Unreal Engine 2....

OS: Windows XP 5.1 (Build: 2600)
CPU: GenuineIntel Unknown processor @ 3003 MHz with 2045MB RAM
Video: NVIDIA GeForce 8400 GS  (8250)

Assertion failed: Actor->ColLocation == Actor->ColLocation [File:.\UnOctree.cpp] [Line: 1703]

History: FCollisionOctree::RemoveActor <- ULevel::MoveActor <- NormalSubUzi37  <- UObject::ProcessEvent <- (R6TMilitant04 Alpines.R6TMilitant31, Function R6Engine.R6Pawn.SpawnRagDoll) <- AR6Pawn::UpdateMovementAnimation <- AActor::Tick <- TickAllActors <- ULevel::Tick <- (NetMode=3) <- TickLevel <- UGameEngine::Tick <- UpdateWorld <- MainLoop
Both Raven Shield and SWAT 4 display crash messages like these, so perhaps it is an Unreal Engine 2 thing rather then specific to RvS/S4, but if it is, I would assume there is a way to turn it off. My feelings: This is good stuff to see if you are one of the games developers or testers—but should _never_ be seen by retail customers! Not only is it Martian to regular people, since we can't go edit and recompile code ourselves, all it does is display information that we didn't need to know. If I was going to do something like that for crash handling in a *release* product, I would probably make it said "Programmer fuck up, please sue the company for idiocy" :-) This seems to remind me, of one time I was on the website of a large north-american company, when for doing nothing at all but routine, their website gave me the most interesting error messages.... telling me enough data to find out several server side paths, there otherwise hidden implementation language, and enough data to clue in on what "stuffs" were being used to make the whole show go. I nearly died laughing lol. Maybe I'm a freak, but I don't think user should be allowed to see developer information in a closed product like that.
post script: this was my 1500th journal entry

No comments:

Post a Comment