el_matarife wrote:CarRepairer wrote:
Yet again I have to tell el-matarife that Simpsons already did it but he likes to speak as though CA doesn't exist and he is the first to come up with ideas that will cause the sky to fall. El-Matarife: It was many months ago that it was done in CA and you see that the world continues to turn and no maps have spontaneously combusted.
I don't care at all who did it first or who had the idea first and I didn't say anything about either of those topics. I am just saying BA should implement them.
I realize in this context we're in the BA subforum whereas the previous time we had this "encounter" was in the general subforum. But my point is you're acting like it's something new and unknown when it's not. So I'm just letting readers know it's possible, has been done already, easy and no harm has come from it. And I agree BA should implement it too as should any Spring mod.
el_matarife wrote:
And you're pretty close to saying "Play CA, BA SUCKS" which this really isn't the forum for.
Nah I'm not saying that. What I'm saying is "SMD numbers suck when Spring mods are different, but the good news is you don't really have to depend on them and mappers don't have to worry about finding a universal set of values as it's impossible."
After all, if you spend hours, days or weeks working on heightmaps, textures, features, metal spots and whatever else, would you feel okay over the fact that some mods can't enjoy the fruits of your labor because you chose a few numbers that only work in one mod and not another? That would be the equivalent of someone making an awesome solar panel model but it's only usable in XTA and not CA or BA because the model is joined at the hip to a unitdef file where the modeler had to choose an energymake value that works with one mod. But it's not, and a mapper shouldn't have to stress over SMD wind values either.
This all began because I'm a huge fan of hunterw's maps. He's not the guru of spring wind values and he doesn't really care. He just makes great maps.