Rapid Brickset Editor 2 (working beta!), Oct 1st.

Yyyyeeeessss...! Finally. I'm cheering right now.

Which Open Surge tools are still under active development?  The wiki lists

Rapid Brickset Editor
Brickset Editor Tool
Level Creator
JBM Zonique
CodeWatcher

The Level Creator doesn't seem to be available anymore?
Language Editor

among the listed, the only active project is RBE 2

My homepage | Rapid brickset editor 2

I computer science.

Bricks draw to the screen faster if they are multiples of 8 and the larger a brick is the slower it loads, the choice of 16 by 16 is a game making tradition and making bricks in these sizes can actually improve your performance by an amount that gets bigger by the brick.

Idk, but it would seam like that's the case.

Listen to my music
Don't miss the facebook group!

I agree with KZR. Brick size doesn't matter; it's how many bricks there are. Quality over Quantity.

I never said I wanted bricks that aren't coordinated by multiples of 8, I just wanted larger bricks.

S32X, have you ever tried Brickset Editor Tool ? It can handle bricks of any size. Very nice tool, but it is not maintained. The program is made by a guy whose nickname is Celdecea. Too bad he is no longer with us.

There was another attempt at building a brickset tool, this time from a guy called MTK358. It could also handle bricks of any size. Unfortunately, it is no longer available. Unfortunately, MTK358 is no longer here, either.

Yes, as lunar has pointed out, my time to work on opensurge is limited. I currently code the engine and work on the game. I also provide users some basic tools, so they can get things going, make their mods, and so on. There's a basic brickset editor (RBE) and a basic level editor (the built-in one), that, although far from perfect, work well for a reasonable pool of purposes.

The main reason why I fixed the brick size to 16x16 on RBE is because is greatly simplifies creating bricksets (it is fast!) and building the tool. Also, using 16x16 implies grid-compatible bricks. Unfortunately, RBE can't handle anything beyond that (other sizes of bricks, movable bricks, animated bricks, and so on). It is not supposed to.

Now, please understand that due to the workload, at this moment I'm unable to provide super flexible tools to modders - which I know they want and need. Now, these kinds of efforts have to come from the community. There's nothing stopping anyone from building better, more flexible tools. In fact, this is encouraged! Please go and make them! However, please do not expect them to come from the engine coder.

My homepage | Rapid brickset editor 2

I computer science.

yes, we know. His tool has crashing bugs and it is not maintained, unfortunately.

Now, the initiative to improve things has to come from you, guys. There is nothing stopping you.

My homepage | Rapid brickset editor 2

I computer science.

Sorry, I was a bit wrong, things that are powers of 2 tend to process faster inside a computer, so we start at 2 then continue multiplying answer by 2 to get 4, 8, 16, 32, 64, 128, 256, and 512.  I've provided a link below that attempts to explain why game designers started using these numbers.  Also, I was not trying to mislead you when I said that engines tend to bog with bigger images, in fact many engines I know of don't have support for loading an image above a certain size to protect themselves from such slowdown.  What we need to do is preform some optimization testing with various brick sizes and see precisely which ones provide the best performance on multiple platforms.  We will need to write some engine code that can catch how optimum our performance is and print it to a readable file which can then be read by the mod developer to help them determine what size of brick they wish to use for their game.

Links:
http://gas13.ru/v3/tutorials/sywtbapa_w … prites.php

Thanks for the link, I agree it makes sense to use those sizes.  Some way to test the engine would be good.   Maybe just try breaking it with tons of bricks or some massive bricks.