@indiGLOW: Yes, it could be useful but i have nothing find how access this block-data in the SDK. Maybe it is not documented, i ask Wlad by time.

@DaBro0zar: I think such a good feature will clearly increase the project size and bsp is a prevent. Perhaps a quick and dirty version.

Being able to bend blocks/primatives or groups.

Stair/arch generator like in 3D World Studio. There's alway's Dan's Arch-E, but an in-editor solution is always best.

Adding a cylinder with a number of sides determined by an input field would be usefull.

old_bill

@Orange Brat: Sorry, there will be no bending. Arc works and with the step-tool you can realize stairs and co.

@old_bill: It is already working with up to 42 faces, more will lead into compile errors. I´am waiting for an answer from conitec about this. However compiler max. faces is 64.

a slice tool would be nice to cut blocks in hafe makes more control to level disign

Here is a MUST for both WED and MED that I was shocked when I found out they didn't have:

We need to be able to manually put in coordinates for whatever we are messing with (whatever we have selected), what would be nice as well is if we could manually input their dimensions (again of what we have selected), if any one of you has Adobe's Fireworks, Flash, or Dreamweaver you know what I am talking about, unforchanately all of that is 2D though so I want it in the 3D world.

Like in Maya?...

@SwordsGateSCAS: Hm, i put this on the very end of my list, if a valid block is sliced, it should give only valid blocks i hope...
I can´t imagine why conitec should not implement this, they have already a complex cut function!?

Hello,

little status, last chance for wishes:

Finished:
100% - disk/pie
100% - arc/torus (made of blocks cause limit of 64 faces and 40 edges by the compiler)
100% - lattice block (made of blocks cause limit of 64 faces and 40 edges by the compiler)
100% - sphere (problems are bsp related, very compiler intensive above 150 blocks = ca. 4000 portals, made of blocks too)
90% - connect faces from two blocks via new block
0% - step tool (like in excel, mark two blocks, and you can pull out other bocks from them with the diffences between the two blocks) or a simple turtle language
50%- place objects on lines/circles
0% - align tool
100% - auxiliary lines/circles
50% - change rotate origin
0% - local rotate/resize for a group of blocks
0% - face block to a point

Started work on the interface, first version should be available next 2 weeks.

An outomated function, that snaps all edges/vertecies of all blocks at once to
a grid, but chooses the closest snapgrid, and not
the next lower even, as it seems to me.
(not like int(3.89) = 3 but: 3.89 -> 4)

Maybe also a warning if blocks are not totally on the grid.

I would prefer to put WED into a mode, where no vertex can be moved to
after comma numbers.
A lot of levels have little cracks, that are a major couse for slow
visibility calculations. Snappin everything to a grid reduces this risk.



Also for texturing:
applying the texture only to the side of the block, that is touched by the cursor.
This makes skinning a block with different textures much faster.

And the option, that when a skin will be applied, that the lower left edge of the texture is
automatically at the lower left edge of the touched side of the block.
Reducing the time it needs to realign the texture manually.