svn12087 crash to desktop

Find any bugs in Vega Strike? See if someone has already found it, or report them here!
Post Reply
whatch1
Bounty Hunter
Bounty Hunter
Posts: 182
Joined: Sat Jul 21, 2007 5:14 am
Location: Western MA

svn12087 crash to desktop

Post by whatch1 »

running the bus route Atlantis to serenity unmoded Lama third run return leg
bam ugly windows error

AppName:vegastrike.exe AppVer:0.4.3.0 ModName: vegastrike
ModVer 0.4.3.0 Offset 0025a8d8
You do not have the required permissions to view the files attached to this post.
Machine: P4 prescott 3.2 Ghz, 2Gb ddr ram, 2 80g seagate sata drives in raiad stripe config nvidia 6600 gt oc card sidwinder pro FF2
loki1950
The Shepherd
Posts: 5841
Joined: Fri May 13, 2005 8:37 pm
Location: Ottawa
Contact:

Post by loki1950 »

Thx whatch1 some more NAN's i see and a few tracebacks should be useful looks like svn12087 may be a dud as both you and CtV are having problems with it.

Enjoy the Choice :)
my box::HP Envy i5-6400 @2Q70GHzx4 8 Gb ram/1 Tb(Win10 64)/3 Tb Mint 19.2/GTX745 4Gb acer S243HL K222HQL
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
bgaskey
Elite Venturer
Elite Venturer
Posts: 718
Joined: Wed Mar 07, 2007 9:05 pm
Location: Rimward of Eden

Post by bgaskey »

CtV's problems are on his end tho. This one looks more like an actual bug. those NAN messages may be ace's idea of more useful warnings, but I don't see anything in the latest svn updates that would cause a crash...mostly data-side.

Code: Select all

NetForce transform skrewedNetForce transform skrewedNetForce transform skrewed
I found this line rather humerous :lol: have no idea what its trying to say tho. that was the last line of stdout.txt
I don't think the NAN's were the problem tho as they seem to be occuring long before the crash.
ace123
Lead Network Developer
Lead Network Developer
Posts: 2560
Joined: Sun Jan 12, 2003 9:13 am
Location: Palo Alto CA
Contact:

Post by ace123 »

Could possibly be related to the same bug causing the NaNs.

I know the collider will sometimes pick invalid polygons, past the end of the array, which could cause a segmentation fault if it goes to far, but at the moment this bug has only resulted in nan's.
Post Reply