Hi, I have a main level that contains many rooms, and those rooms are just a single separate WMB map entity, (Hope I haven't lost anyone yet). In that small map entity, I have several models placed, However when I run my main level, the rooms are created, but their models are not created.

In the main levels code, right before the main WMB is loaded, I have map_subents = 1; However, no subentities are created. Why?

If you need any other information that I may have missed, please ask and I will gladly provide the information.

P.S. I'm using A8 free.

Apparently map_subents only has an effect on map entities created with ent_create, not on those which have been placed in the level in WED. I think this is a bug and you should report it.

This is correct looks like a bug. I faced this problem a few weeks ago. But i did not know the ent_create "trick" , thank you for that tip.

I've found a simple work around using the ent create trick, however, the models contained in the room, do not rotate along with the room. is there a way to rotate the model with the room like it should?

Sure, why would they rotate with the room?
You can of course realize this by code, for instance by saving the subents (pointers to the entities) in the skill array, vec_diff their positions and save their original orientation. Then, when you rotate the room, calculate their new positions and rotations with vec_ and ang_rotate.

I would think they would rotate with the room because they are placed in the room via WED and then saved as a whole as a map entity so as it's created, the models are created with it, so logically if you move the room, the included models should move to, not individually by default. Controlling them separately should be optional. Since i'm not familiar with all of the vector manipulations, I'll have to come up with a different solution.

Saving and compiling them as a map entity is the same as when you build a regular level, the meshes don't get merged but just the information where which entities need to be created with some initialization information gets saved, not more.

The vector-solution is an easy, relatively fast and flexible solution, you should give it a try.
One hint:
vec_diff(my.skill60,my.x,my.parent.x); // once at the start of the action
...
vec_set(my.x,my.parent.x); // in a loop
vec_add(my.x,my.skill60);

The code above is a very simple way to keep a non-rotated entity at the same relative position in respect of the parent entity (your room), even when you move the latter.