It wont allow us to put 2 weapons on that automatically,they are just 2 'invisible' hardpoints,only useable when the droid's 'numWeaps' > 1/body_size > SIZE_LIGHT.Troman wrote: What about creating and loading new save games, do new savegames work properly?
Do all bodies need 2 connectors, even tiny ones? Will that automatically allow us to put 2 weapons on them?
they look ok,I made the 2nd one 'embbed' into body(slightly higher than VTOL weapon),and 3rd one is slightly higher than 'main turret',since the all bodies except dragon is too 'narrow'.I really don't know if Medium and Heavy bodies can handle 2 and 3 turrets, respectively. I mean that will probably look ugly with most of the weapons. I think it will be better if we add new bodies for this purpose, some fresh wind so to speak.
I have created an overview of body data for this purpose, for an easier orientation:
http://wz2100.net/wiki/user:body_table
new bodies will be great,but large bodies might cause collision detection problem?,I dont know how they detect the collsion of a droid,if they use the points in a pie to detect collision,then it shouldnt be a problem.
It's in bodies.txt.Where is engine output defined, in propultions.txt? Was it completely unused up till now? Are you sure 50% is not too much? We don't have as many Schumachers to put them into every single tank.
We should probably fuzzify this engine output/speed bonus relation.
yep it was completely unused,the only reference in source was in the design windows,there is a stat 'bar' in body selection step displays engine output.,but that's all.
50% just a test value I thrown in to test whether it works or not,yes it does work,there are speed caps for all propulsions,even with 50% bonus it wont exceed the caps.
Initially I wanted to make the bonus value the result of 'engineOutput/totalWeight',but the bonus will be either too small/too big,it's 1.5f atm.
Maybe giving the droid other bonuses based on engineOutput will be interesting too/might help balancing the bodies.
hmm I will look for the template list and see if I can make the AI to use the new designs.AI uses pre-defined template list.
Now that's a problem. ;D
the patch is created with TortoiseSVN,or I can send you the modified sources/pies,patch is alot smaller in size though,patch compressed is only a few KBs while the zipped sources+pies weights 300+KBs.Though the patch might cause conflicts if you make changes to the source recently after rev 431.Besides,you need a modified resource_parser.c if you want to compile it in windows,some recent changes broke it,physFS will freak out if you dont replace the '\\' with '/' in that file in windows.I don't know about this, I don't have a tool to apply patches, unless the patch is done with TortoiseSVN, maybe Devurandom can do this when he has time or you can create patch with TortoiseSVN and I can look at it.