Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[pasto]

Here is the link:


Basically what has been done so far:

- new UI framework to render dialogs (Javascript)
- sketch API to draw lines, images (C++)
- new 3D scene widget framework (Javascript)
- new camera controller to better suite the editing needs (non-linear zoom, smooth transition between different panning modes for different zoom levels, automatic / manual focus point)
- basic select / multiselect
- cursor showing elevation, distance, current axes
- camera / environment / time settings
- new entity / object browser with possibility to place objects
- object move operation with basic snapping (protractor / compass), cloning
- 3 different operating modes (copy terrain elevation / keep the sea level / align with object axis)

We have also migrated some of the dialogs to the new UI framework:

- location browser (already released)
- fbx importer
- object browser
- key binding editor

As there is still quite some work to be done to have all the functionality of the old UI, we will release the new sand box as a WIP in parallel to the old sand box. We would like to do it as soon as we have it stable, hopefully within next 1-2 weeks.

Some more pics (http://imgur.com/a/GeLTX):

[necro]

Wow, thats really impressive!

[Levi]

Awesome! I'm lovin' it!

[booz]

!!!! Woooww.... impatient !!!!!

[Acetone]

✓ Nice UI
✓✓✓✓✓ Object cloning
✓ Multiselect
✓ Info on cursors
✓ All useful tools/data in the same window

→ That's fantastic!

Looks like my WIP scenery tutorial will need some updates

[HiFlyer]

Looks good. 

[Varldsligist]

[ZeosPantera]

PAstO!

[Revolver]

Aaaaa ... very good, Pasto! On something I've been waiting soooooO long ...
Thank you very much!

[KW71]

Bravo, pasto!!!

Looks great!!! Thank you very much for this!!!

[PytonPago]

A little menu ... will there be some Sub-menu extnsion for obiects, that have several versions ? ... i mean, like the Tatra vehicle - if another version (as there are two) are defined in the same directory, it could open up a sub-menu, that will give the options for its variations - this way, even for my ural, jus one would be shown in the main menu, but all its variations, defined whytein its folder, would show up in the sub-menu ... would clean up the main-manu up a lot

[pasto]

Currently the objects are grouped by skins and packages so in these cases it should create a folder like structure if there is more than one item in the folder and together there are more than predefined number of items that  satisfy the filter.

[PytonPago]

Currently the objects are grouped by skins and packages so in these cases it should create a folder like structure if there is more than one item in the folder and together there are more than predefined number of items that  satisfy the filter.

Has right ... (didnt really mention that entities pannel in the first screen) ... great news then ! Stil, is there an thought about somehow differentiate pure skin-difference and a model-set difference ? Lets say you have 3 skinns and so you have 3 .objdef files there in the folder, but yet, there is also another variant (the tatra with and without the bed or more complex stuff like that Ural of mine) ... it will be, as it is now, each of those variants (each with its own .objdef) also dumped into this sub-class together with the purely skin-differentiaded ones.  For me now its ok, but if one day someone would like to extend it to 1st "foldering" as variants of the model and 2nd as diffenent skins of one of the variants ? (this would probably need a change in the .objdef file definition parameters - adding something saying if its ust a skin and of witch variant, or an else variant)  ... its probably true, that in real-life, no one does models the way i did the Ural and different variants are then just imported each as a different package (meaning, its probably useless to try doing such a thing, creating just an annoying parameter), still maybe differentiating ground-vehicles in the future would come along anyway (diggers, sport/racing cars/ tracked vehicles etc.   or aircraft into propeller/jet-engine like separation), so do you have any ideas into the future for this ? (if your aim will be to do such a thing someday for the combined simulator maybe)


 ... or just something searchable maybe ... a section for "key-words" that would each content-creator add in the .objdef and the menu search-engine would just look up all fitting objects for it. Such a mini-google purely for the content installed.

[Levi]

... or just something searchable maybe ... a section for "key-words" that would each content-creator add in the .objdef and the menu search-engine would just look up all fitting objects for it. Such a mini-google purely for the content installed.

I think this is already there. Look at the screenshot with the Object Browser, there's a search-box on top where you can enter keywords to filter the objects. And I guess that the search engine/filter is looking at the tags inside .objdef files.
You already can add tags in your .objdef files btw:

Code: [Select]

"tags" : "ural"

[PytonPago]

... or just something searchable maybe ... a section for "key-words" that would each content-creator add in the .objdef and the menu search-engine would just look up all fitting objects for it. Such a mini-google purely for the content installed.

I think this is already there. Look at the screenshot with the Object Browser, there's a search-box on top where you can enter keywords to filter the objects. And I guess that the search engine/filter is looking at the tags inside .objdef files.
You already can add tags in your .objdef files btw:

Code: [Select]

"tags" : "ural"

Oh .. than its all ok ... (man im blind today)