Re: Room Editor De Fotos
Nandan Barahona
The Room Editor is where you create your game rooms. Every game requires at least one room to run, and in the room you can place instances, sprites, tiles, paths, backgrounds, sequences and particle systems. Each of these different assets can be placed on their own unique layer which can then be ordered however you wish in the Layer Editor. Due to the complexity of the Room Editor, we'll give you first a brief overview of the most important features, and then you can find more in-depth details from the section links listed below.
When you create a room asset, you can right click on it in The Asset Browser to open the context menu, which will permit you to create child rooms (see the page on Room Inheritance for more information), open up the room for editing, add a new asset group to better organise the rooms, rename the room or delete it. Note that to change the room order and/or inheritance you need to use The Room Manager, which you can open using the menu in the top right of the Asset Browser.
The Room Editor is itself a workspace and as such you can click on the tab and drag it off of the main window into a new window of its own - perhaps in another display, for example. You can also place it back into the main window by dragging the tab to the top of the IDE and releasing the mouse button.
The user interface for the Room Editor is simple to navigate and split in various discrete sections. Those parts of the editor that are docked - The Inspector that shows the room or layer properties and the Layer Editor - can also be removed from the dock by simply dragging them out into the workspace, and they can be added back into the docks again by dragging them to the sides or the bottom of the workspace.
I have been looking for a way to add images ( .png ect) to walls or add text to a wall. I have seen this on numeorus clubs but there is hardly any information on how to do this. I have no problems with hosting the images. seems like you can do many things with world editor.
Its ok I got it figured out that you need modz and hacks...most of all any thing that can save images and files to .world extension................images and text...how hard can this be to implement in world editor!
What now? If I understand correctly, it is possible now to create a gallery with this. I mean a gallery room, with that ''Tamara Tool'' or ''world pic''. And the pictures in game..they will look like photos or will they be transformed into some tetris look or how to saaaaay . Are the sizes of these images very large? I mean, hypothetically If I would add 10 of such pictures to a room, would I need then a computer from NASA to load the room or everything would work just fine with my normal pc?
have u bothered See the amount of props its creates for a 100x100 pic simple math for a picture in a wall that 90 % of 3dxchat player base wont even be able to see and in best case it will be seagmented or the file size of that pic will like 1-2 clubs lol please ...
Rooms are the spaces where your actual game happens. A room can represent a level, a menu, a UI widget, and is a place where you place your copies (instances of your templates), backgrounds, and tiles. Knowing how to use it to the fullest will ease the level design process.
Then select a tile on the texture you've imported and place it inside the room with a click. You can also select multiple tiles by pressing and dragging your pointer across several frames. After that, draw with tiles with your mouse.
Creating a ton of layers is also not recommended, because 1) it is dumb, and 2) each tile layer caches its contexts to boost rendering performance, and if you do use tons of layers, it nullifies the performance boost and worsens the situation with RAM.
You can also change values in the properties panel on the left, but note that contrary to the selection frame which transforms everything as a group, the properties panel changes values for each object individually.
Backgrounds are added in the fourth tool of the room editor. Inside it, there is a button "Add a Background" that opens a texture selector. There are several things to consider while using backgrounds:
The panel that is underneath the buttons occupies exactly 50% of the screen. Its alignment frame has default settings, as it is positioned relative to the viewport, and its constraints lock top and bottom sides, so there is no gap, and horizontal constraints are disabled, so the panel stretches with the viewport and continues to cover exactly 50% of the screen.
All the buttons have horizontal constraints so they stretch horizontally nicely. Top buttons have top-side constraints, and the bottom one has bottom-side constraint. This makes them stick to top and bottom sides of the panel respectively.
Bindings are used to automatically change properties of copies once the value in the binding expression changes. This can be used to make dynamic text labels without having to create a separate template, or to, say, change button's color when certain conditions are met.
If you create a new repository, the Page Builder will be activated by default. However, we can disable it for your repository on our side. If you would like us to disable it, just submit a request through our support portal:
It has been my experience that when you click the pencil and are not given the option of what type you want to create, this is due to the fact that I've had no other possible type I can make. For instance, I have a "settings" custom type (single), "homepage" page type (also single), "page" page type (repeatable). If I've published my settings and homepage documents and then click the pencil to create a new document, the only thing I could possibly create would be a Page so it takes me right to it.
The new editor really does not feel like ready for release.
The first round we got it forced upon us, we actually had to ask you to set the legacy editor as default, since we had breaking bugs in the new one (the legacy slices could not be added and tabs design could not handle more than a couple of tabs before it screwed the entire page).
For a second time, we are forced to use the new editor. The breaking bugs from last time are gone, so this is good at least.
Since I get the feeling that the legacy editor is living on borrowed time, Im trying to use the new as much as possible to get used to it. When teaching our editors how to use the writing room it is now in the new version. This makes the following limitations worse, because it is hard enough to get our editors to understand one version of the writing room.
To have to tell them "To do this, you have to go into the Legacy editor", which looks completely different is not feasible.
I find this thread that has been active since 2020, and I really hope the new Rich Text editor will enable you to add new features, because right now this feels like a step back. For example I had one editor that needed help finding the formatting options, as it was not intuitive that one had to write "/" or mark the text to trigger the overlay.
Slugs. Yes, I know these has been deprecated for a while now. But I guess what Im missing is a heads up before the slug suddenly is replaced with a "-" when saving a document in the new writing room. This created breaking bugs for us.
The new editor is also missing the rich-text "Labels" features... It's also quite slow to load, IMO.
Can you please make it easier for one to enable legacy by default? I am happy to give some feedbacks, but honestly hitting "Legacy editor" dozens of times a day is painful. It makes us lose a lot of time.
Not many people will be as lucky as me, I guess. Some of you might be able to find a windowless nook in your home, away from that nasty changing sunlight. But most of you will have windows to contend with. So you have to do the best you can.
My lighting store guy was very generous with his advice. He told me that among modern bulbs (LED and fluro) we should probably look for temperature of 4000-4200K. Lower would be too yellow, and higher too blue. He said to be wary of descriptions such as "Daylight" and "Cool" as their meanings could vary between manufacturers.
He told me that the brightness was measured in Lumens, and usually we would look for bulbs in the 600-900 lumens range. But he hastened to explain that the brightness should be dictated by the size of your room and the height of your ceiling. Whereas a single 600lum bulb might be ample in a small alcove, it would be pitifully dim in a larger dining room, for example. (He loosely suggested a total of 1800lum for a standard 4x4m bedroom, from either two 900s or three 600s.)
We're now seeing an explosion in Smart LED light bulbs, which let you change their temperature with an app. I haven't had a chance to test them in an editing area yet, but I think they might be the future of office lighting for photo editors. Being able to choose the colour of your lighting sounds very promising.
I have a 3d online room editor (written in babylonjs) each room is represented by a JSON and an item is a .babylon file (we can also export it in a different format if needed)
Babylon really does the trick when speaking of real-time editing of the scene but we want to export much more realistic 2d images out of those scenes, and I assume it will be easier (and maybe even possible) to do in the backend using different rendering engine that can do ray tracing and other tricks.
I do understand that rendering the scene in such engine will take time (much more time than 60 per second).
Does any of you guys ever done something like it? can you recommend on rendering engines that I can programmatically wrap and generate those images? (no limitation on programming lang) any suggestions will be welcome.