The Chaotic World of Crime is taking over, be a enforcer or lawbreaker, take down everyone, zombies, people, and lots of bad monsters.

Post feature Report RSS DATA LOST SSD DRIVE DEAD burned by new weapon_cw_flamethrower

yes finally CrimeWars has a flamethrower that can burn things, it even burned worldspawn and crashed the game. oh wait, it has the debug binary for it but not the code anymore! Well it can be recoded in a few hours again. Its alright. Also code was backed up a few days ago to the SVN so most things are fine. The flamethrower is attempting to burn prop_physics, prop_dynamic, mostly everything has to be burned down. prop_vehicle_jeep or prop_vehicle_sedan still has problems burning.

Posted by on

after prop_vehicle_jeep/sedan lights on fire once, it fails to light again, notice in the videos, how I do a sneaky thing of not really showing that. Also I noticed some other props crash the flame code, I can't know what they are til its recoded again, because can't debug without code.

Note: worldspawn was burned by pointerCWorldObject->Ignite(LifeSpan, true, FileSize,false);// illegal operation

Also there is other mission impossibles in the coding process, the infamious prop_flex_vehicle code for sedans and some other vehicles, which will require some crafty modeling with flex/morpher modifier in 3dsmax.

And c_models! also, working on a automated script to help make the qc and smd files of existing models to be converted into multiple hand model animations working together.

I think theres more random crazy projects, I'm just awake all night and can't remember a damn thing right now. Some random map development in some video.

Note: about SSD harddrive failure: SSD is a very unstable storage, NEVER store anything or Develop anything ON it, I had to learn the hardway, I was abuse that drive, with a deranged mind set, pagefile.sys was on there, and windows would crash, because of bad ram, and I'm thinking also maybe SSD was begining to fail, but worked like it wasn't the problem. Well windows would just reboot at login screen because SSD drive was forable set to be pagefile.sys ( the Drive drive RAM temp file ), and that also caused me a night of confusing, and running diskchk and other windows repair tools, that didn't do much... because it was a setting it couldn't really detect, anyway, SSD is too much money, and look up SSD Data Recovery, its a scary horror cyber movie for various reasons.

Post a comment

Your comment will be anonymous unless you join the community. Or sign in with your social account: