*Snip* - Neddiedrow
Acutaly smf isn't and sm3 is, however sm3 is buggy and doesn't work with a lot of people machines. JC has also decided to abandon it.
SM3, SMF & Collision Issues
Moderator: Moderators
-
Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
Re: Flames brewing...
Take It To Teamtalk - Neddiedrow
The wall was an example, an example that you are arguing for some unknown reason. I am saying that working around the issue is no longer an option. You seem to presume that I will not or have not tried to work around it. I have and I am saying that the solutions are unacceptable, that is all. Just as the melee solution is unaceptable, so is the current collision system.
The wall was an example, an example that you are arguing for some unknown reason. I am saying that working around the issue is no longer an option. You seem to presume that I will not or have not tried to work around it. I have and I am saying that the solutions are unacceptable, that is all. Just as the melee solution is unaceptable, so is the current collision system.
Re: SM3, SMF & Collision Issues
Its been discussed, and the tiling system in mapconv is fail. Its great for metal maps that use the same texture over and over again but for a normal map it just wont do. A useable SM3 would be very nice for all the reasons smoth said. Shame its been abandoned (That is if what forb is saying is true).
Sphere collisions seem to me like a quick fix, and nothing to do for long term. Because well... how many units in Spring are actually in the shape of a sphere? Nothing in any TA mod I can think of, though I guess the Kernal Panic Byte is set for life.
Sphere collisions seem to me like a quick fix, and nothing to do for long term. Because well... how many units in Spring are actually in the shape of a sphere? Nothing in any TA mod I can think of, though I guess the Kernal Panic Byte is set for life.
Re: SM3, SMF & Collision Issues
well lordo, kloot was working on a patch for the collision.
as far as sm3, we are just waiting for a dev to take it up again.
as far as sm3, we are just waiting for a dev to take it up again.
-
SwiftSpear
- Classic Community Lead
- Posts: 7287
- Joined: 12 Aug 2005, 09:29
Re: SM3, SMF & Collision Issues
I'm so frigging close to banning you all for being retarded.
You realize you're arguing over which is a BIGGER issue... something that is inherently subjective. We have many issues, and you can explain them in minute detail until you are blue in the face, but weather the mechanics of an issue make it "bigger" than another issue, is completely a matter of opinion. There's no point in explaining why hit detection is broken, we know it's broken. There's no point in explaining why SM3 is a nicer map format than SMF, we know it's nicer. There's no point in explaining the limitations of building single player content, we know there are limitations. The issue being discussed here is which issue should take PRIORITY, the mechanics of the problems are all but utterly irrelevant.
I can appreciate that smoth wants more realistic hit detection, it's a pressing issue for his project, I can appreciate that he wants SM3 mapping, I'd really like it myself, it's a much superior mapping system. I can appreciate that forb wants single player functionality, it's an incredibly important project... but seriously, to argue over which is the biggest issue... As if the result of this argument will acctually change the fact that the people developing are doing whatever they are doing... and that's assuming a real result is even possible.
You realize you're arguing over which is a BIGGER issue... something that is inherently subjective. We have many issues, and you can explain them in minute detail until you are blue in the face, but weather the mechanics of an issue make it "bigger" than another issue, is completely a matter of opinion. There's no point in explaining why hit detection is broken, we know it's broken. There's no point in explaining why SM3 is a nicer map format than SMF, we know it's nicer. There's no point in explaining the limitations of building single player content, we know there are limitations. The issue being discussed here is which issue should take PRIORITY, the mechanics of the problems are all but utterly irrelevant.
I can appreciate that smoth wants more realistic hit detection, it's a pressing issue for his project, I can appreciate that he wants SM3 mapping, I'd really like it myself, it's a much superior mapping system. I can appreciate that forb wants single player functionality, it's an incredibly important project... but seriously, to argue over which is the biggest issue... As if the result of this argument will acctually change the fact that the people developing are doing whatever they are doing... and that's assuming a real result is even possible.