-an easier way to set up views which render only particular entities like bounding geometry for lights by f.i. filling a view associated list with entities
-texture coordinates which are always in the range 0..1 for pp-effects, which is not the case atm. I don't see much sense in this design choice. It annoys me.
-making it possible to use a custom vertex shader for pp-effects

The first one would actually be sufficient.

-a list for entities which can contain multiple materials and associated views, for render view dependend materials

I really don't like to handle view-dependend rendering over material events.

And of course DX11.

Do you know the following approach?

VIEW* my_view with NOENT and NOWORLD set, then after level_load
my_view.genius = ent_create(NULL,nullvector,NULL); //or any other entity
and finally set every entity's parent pointer to my_view.genius which should be rendered by that view.

No, I actually didn't. ._.°
That's nice! Thanks for the hint.

@Superku: OH, what a gem of a tip

The best thing for me would be a publish option for more systems like MAC or consoles!

That would be nice, indeed but I think at the moment they should concentrate mostly on the PC.
More platforms require A LOT of work but they won't make the engine better and I think only a few people would use this.

There's so much outdated stuff which really needs to be renewed. (the default lighting system didn't change since A5 afaik)

So, the most important thing in my opinion is, that the Acknex Engine will reach a state where it is competitive to other engines.

Please keep in mind that you have to support this platform as well, which means that you need hardware to test your game on and you need to know the platform well enough to give support to your users.
This is coming from someone who is currently working on a project that runs on all major desktop and mobile platforms, and I wouldn't dare to support Linux and Android if I wouldn't work with someone who has experience on these two platforms.

And while an engine can abstract you a lot away from the underlying hardware, you still have to keep certain things in mind (okay, Mac OS X nowadays is x86-64, just like Windows, but on consoles you are suddenly faced with PPC CPUs and if you want mobile you suddenly have to deal with weakly ordered ARM CPUs. Changing platforms is no kindergarten, it's the exact opposite).

@preacherX
...and if you target to release a game which should be available for Mac, ask yourself the question if it's really worth all the work.