Spring RTS Engine

So many of mapping problems could be solved if we used SM3... so why dosn't anyone? Is it broken and I'm not aware of it or somthing?

It is broken.

because its not reliable, for instance i can't run SM3 maps on my ATI Card with shadows enabled,

all maps have to be square, so 10x12 is not possible, only 10x10 or 12x12

And some other issues i forgot

neddiedrow wrote:It is broken.

This sums it up...there are a large number of issues with it, including a crashbug that makes them pretty much completely unplayable on gf8's which makes Peet cry T_T.

Making sm3 maps take a little longer to
make. Also, there are some issues that
need to be resolved.

Only time will tell ...


Hopefully things will get resolved in the come weeks ...

genblood wrote:Making sm3 maps take a little longer to
make. Also, there are some issues that
need to be resolved.

Only time will tell ...


Hopefully things will get resolved in the come weeks ...

Ugg, ignorance. If you know what you're doing you'd be able to finish an SM3 map before the frigging slow arse l3dt texture map is finished rendering.

SwiftSpear

Ugg, ignorance. If you know what you're doing you'd be able to finish an SM3 map before the frigging slow arse l3dt texture map is finished rendering.

I make a simple statement that the process is different from making
maps. An I get CRAP ... about IGNORANCE ...

I don't even use l3dt ... when I make my maps ... for your information ..

I use MS Paint, Gimp2, DTXBmp and Bryce5 ... I was using simple
bat files to combine it all together ... Right now I'm using TASMapMaker
due to it's easier to use and it works great ....

genblood wrote:SwiftSpear

Ugg, ignorance. If you know what you're doing you'd be able to finish an SM3 map before the frigging slow arse l3dt texture map is finished rendering.

I make a simple statement that the process is different from making
maps. An I get CRAP ... about IGNORANCE ...

I don't even use l3dt ... when I make my maps ... for your information ..

I use MS Paint, Gimp2, DTXBmp and Bryce5 ... I was using simple
bat files to combine it all together ... Right now I'm using TASMapMaker
due to it's easier to use and it works great ....

Then the process should be virtually identical, aside from with SM3 you never have to deal with single million x millon pixel texture images.

SM3 is not usable, Swift.

neddiedrow wrote:SM3 is not usable, Swift.

But more importantly:

FIXIT

neddiedrow wrote:SM3 is not usable, Swift.

That's because the format is broken, not because developing an SM3 map takes longer than an old format map. You can still develop SM3 maps if you'd like, but they won't be played because of how poorly they work in game currently.

SwiftSpear wrote:

neddiedrow wrote:SM3 is not usable, Swift.

That's because the format is broken, not because developing an SM3 map takes longer than an old format map. You can still develop SM3 maps if you'd like, but they won't be played because of how poorly they work in game currently.

Interesting. Seems like a waste of time.

Well, if you can find a developer to finish SM3, I'll learn it. I haven't been able to find anybody I could sell on the idea for six months.

To many problems eh?...well thanks I guess. It makes sense that its broken since no one uses it. I was just curious becuase im currently making a 24x24 map but its so big that theres no chance anyone would download it x_x. I was considering SM3 if it would help reduce my filesize a lot.

LOrDo wrote:To many problems eh?...well thanks I guess. It makes sense that its broken since no one uses it. I was just curious becuase im currently making a 24x24 map but its so big that theres no chance anyone would download it x_x. I was considering SM3 if it would help reduce my filesize a lot.

Well, mostly it's broken because jelmer never got around to the full scale playtesting phase of development after he had it pretty much functionally implemented. I mean, right now you can play games on SM3 maps and whine about how broken they are, but it won't be fixed because active development on the system has stopped. JC is doing other stuff and no one else is willing to pick up where he left off. The bughunting phase of a project can be really boring.

Boring is one thing and potential devs not having every possible graphics card is another (see 8800 problems.)

8000 series you mean



lets see problems with sm3:

The terrain tears on deform.
the format runs slower then SMT! UNPOSSIBLE? No it does.
the terrain cuts off very hideously at long distance
just loading an sm3 I take a chance of my machine crashing, locking or rebooting


mmmmmonster fail format.

- removing bump mapping should give a good fps boost
- jelmer fixed the deformation terain tearing months ago, its in 0.75b1+2 now.
- I have no crashes save the usual tdr crashes with sm3 atm.

ORLY?!?! I am testing brb, save my seat!

*back from my system stop error, thanks for that*

Oh yeah it runs fine, then I shoot the ground and my machine CRASHES.

no it is broken.