Thea Render is about to be launched..(edit available now)
-
Hi tallbridgeguy,
Just had to say that I loved this:
@unknownuser said:I don't need or want big push me buttons but I don't need to fly the shuttle either
That is probably the best description of how I would like the UI on all software to be.
There should be a law that this quote should be fixed to the top of the display monitor of every software developer.
Regards
Albion Man -
Maybe we can help Giannis by posting here
-
@jenujacob said:
Maybe we can help Giannis by posting here
Not just maybe...
Please submit your ideas to improve the workflow... -
Frederik
OK a quick shortlist for the UI only.
#1 is user defined keystrokes.
Almost every well configured program has this option.
UI
2-Very dark and hard to read/see and while helped by selecting the Maya option this was just a desperation try and why "Maya" to select.?
Why not a "skin" option for interface color scheme or at least a (white/black) type screen option.
3-Icon bars need to be larger or re-sizable to be quickly usable and understandable.
4-Text for selected icon bar should be at the selector pointer not in an unrelated screen place (center/left ?)
5-Scene/camera should upload to screen with a simple double click.
6-[Select Window/More settings] to get a basic fcn like textures should be part of the default setup not in a buried menu selection.
Also show/hide for textures/materials/ etc menus please.
7-Easy navigation is KEY and having to access multiple selections from the Icon bar is a real pain.
Most applications use the mouse with Alt/Ctl/Shift options by simply clicking on the screen.
(a keystroke option for select would be an easy fix but user defined)
8-Rt click contextual menus for selected options/fcns are a gotta have for a more intuitive workflow.
9-On screen sun selection and move should prevent entity selection when invoked and be much more readable to boot.
10-Keystrokes again.dtr
-
Thanks, dtr...
Much appreciated...
I've posted your input in the Thea Forum -
Hi all. Glad to read that Thea's causing so much agitation! There is some sort of saying that sais something like "it's no matter if it's good or bad, we just need people to be talking about us". Well, in this particular case, I believe good words are a lot more than "bad" words about Thea. About all suggestions posted here I think Thea's team will be delighted about having so much comments and suggestions. As a closed beta tester of the application (yes I am one of the lucky ones
) I may say that what impressed me most is having the main developer asking our questions and doubts in a few hours, sometimes minutes. That proved something - that finally people are understanding that having a community helping them with the development will actually make the applications better suited to the real needs. I just wished 20% of the companies out there were like Thea's team.
Well, now that the beta is open, I suggest you all keep trying. And Thea's made some huge leaps with testers opinions, so I believe it will continue that way, so keep on suggesting improvements.
Overall, at this point, I sincerely say that Thea has impressed me much (I was a Kerkythea fan previously, and I have also worked with vray, mentalray, indigo and maxwell). The features it has today (and will have) and - omg the introductory price (which I suggest you take a good look at) - just made it a must-have for anyone (fanatic like me) for communicating architecture and spaces.
Sorry for the long boring text, but these are all sincere words. Be well all, and see you soon. -
Well.. reading some of the previous comments I have to say that I'm not a "renderguy" but like to stay updated and play around with it from time to time!
I've bought Thea Render because I found the UI and workflow nice and easy, It didn't take me long to make nice results, but of cause I'm not used to other renders. (Ok.. I have twilight two)
The texture editor is well hidden, and som shortcuts would be nice, but I bought the software because I can use it now and that it has a promising future where many of the small "beta-lacks" will be eliminated by the very involved developers. Also the announced roadmap told me that this is a software to rely on!
Maybe I could get on the Thea payroll
-
Frederik
You are most welcome.
dtr
-
Thea is desperately in need of a couple simple video tutorials that show you how to open a model in Thea and render it.
I go to File / Open and select an OBJ file of a simple workbench and, well, I don't really know what happens. I don't seem to get anything in the viewport and I don't know what to do next.
I guess I'll have to read the manual which is hardly too bitter a pill to swallow but a couple videos covering the basics wouldn't hurt at this stage of the software. -
Thanks Albion Man! I appreciate the comments.
On videos, I am teaching a class in structural analysis at the local university and I have been using camstudio to make some decent "help" videos. The students seem to like them and they are used to seeing "youtube" everywhere they go...
I think videos would be a great solution.
TBG
-
I can assure you that video tutorials are in preparation...
Primary reason why we haven't made any video tutorials at this point is simply caused by the fact that the Thea UI isn't completely finished...Once we're closer to releasing the first version, please be assured that many video tutorials will become available...
@arail1: Why do you want to use OBJ files...??
I assume that you have SketchUp, so why don't you use the SU2TH plugin...??I apologize on beforehand... It is not my intention to sound annoyed and also not my intention to offend anyone here, but... Trying to excuse that some users do not want to read a manual is utterly ridiculous...
If you want to learn how to use any application, it is a necessity to read a very simple manual or a couple of tutorials...
I don't know anybody using i.e. Adobe PhotoShop, who haven't read through some simple manuals or tutorials to get some basic knowledge...
Sorry guys, I just don't get the rant - especially not since Thea is only in first open beta stage...
I feel that the Thea team and in particular the developer is VERY open to criticism (constructive) and is also very open to new ideas that obviously will make the workflow easier...
-
Frederik -
I understand the impetus for your post but I think it's a misunderstanding.
I wanted to try to use OBJ files because I'm comparing VRay and Thea for a possible purchase. The problem I have with VRay is that it's locked to SketchUp but I want to be able to use 2 or 3 modeling programs. I'm not quite clear about whether Thea has the same limitation or not, the manual didn't help out there.
Manuals vs video tutorials -
Most software is designed and marketed by extremely advanced computer users. And the loudest voices on the forums driving the development of the software tend to be also from very advanced users. The problem with this is that very often these same people are not particularly good teachers. The ability to present material in a way that a novice can understand, or to even remember what questions they had when they were novices is actually quite rare. Thus the poor quality of most training material.
I skimmed through the manual and it's very detailed but it didn't help me at all to get started. I still contend that a couple simple, basic tutorials that do not go into depth, do not go into complex technical detail, do not explain ad nauseum every panel and widget on the screen, but instead take an object or a scene and explain step by step how to get it into Thea, how to change a couple of materials, how to add or remove a texture will be more useful for novices than the manual in it's present state.
This was not meant to be a criticism - just a suggestion going forward.
-
As we all know Thea is still in Beta and tutorials and PDF's are still being created, the reason there is not much around is the UI has changed and new things are being constantly added, so the tutorials and manuals I saw four months ago are no longer relevant today as things have improved, work-flow streamlined, UI tweaked.
Once the UI is finalised I can honestly assure you that comprehensive tutorials and manuals will become available as well as a repository of materials created both in-house and by community collaboration.Regarding importing models, SU has a very serious poly limit problem, we all know it, in fact rumour has it that even Podium is going studio because of it (too bad Google does not give this issue more priority)
So where Thea can have an advantage is for either using proxies (implemented very soon into exporter) or doing straight 3d imports using .3ds, .obj etc.Take for instance this scene, the house is SU, but the trees (3D) are merged in Thea, Just one tree will buckle SU to collapse (79mb) I wanted 7, so I merged the model with the SU model in Thea, and positioned , rotated in Thea with ease.
Raw Thea render (no post processing)
-
@solo said:
Take for instance this scene, the house is SU, but the trees (3D) are merged in Thea, Just one tree will buckle SU to collapse (79mb) I wanted 7, so I merged the model with the SU model in Thea, and positioned , rotated in Thea with ease.
Raw Thea render (no post processing)I like this rendering. Where did you get the grass texture? If that's one thing I wish Thea had, it would be more outside-ish materials built in.
Rick
-
@unknownuser said:
I like this rendering. Where did you get the grass texture? If that's one thing I wish Thea had, it would be more outside-ish materials built in.
Thanks.
The grass is a simple CG textures diffuse with a noise displacement map.
I will be optimising a few grasses I have made during beta period and making them available soon, as well as a whole bunch of other materials. -
@solo said:
Regarding importing models, SU has a very serious poly limit problem, we all know it, in fact rumour has it that even Podium is going studio because of it (too bad Google does not give this issue more priority)
So where Thea can have an advantage is for either using proxies (implemented very soon into exporter) or doing straight 3d imports using .3ds, .obj etc.Thanks. That's the information I was looking for. I don't create the sort of extraordinary images you do, and maybe never will, so I don't have so much the poly issue but I have the 'models spread over several different software applications' issue. Right now I have a client talking to me about a design for a stair that could use some objects I created in SketchUp but also some objects that are in modo. Instead of going back through one or the other I'd ideally like to take things from each application out into one renderer - which I guess Thea could do if I read your post correctly.
-
You are correct.
With all the exporters available and under construction soon you will be able to take a C4D model, XSI model, Maya model, Max model, SU model, Modo model, MOI model, Z-brush model, etc and merge them all into one scene and render in Thea.
-
@arail1 said:
Thea is desperately in need of a couple simple video tutorials that show you how to open a model in Thea and render it.
I go to File / Open and select an OBJ file of a simple workbench and, well, I don't really know what happens. I don't seem to get anything in the viewport and I don't know what to do next.
I guess I'll have to read the manual which is hardly too bitter a pill to swallow but a couple videos covering the basics wouldn't hurt at this stage of the software..obj should load fine in Thea render and when using 64-bit version I have not yet find a scene that is not possible to open or render... sure there must be one
Do you see base grid after you opened the .obj. If you don't see the grid, it could be some OpenGL clipping issue (scene might be huge). Try to use scale 0.01 when you open the scene. Possible you need to swap axis too. If you still don't see anything, you might have find a bug. -
BTW I'm not trying to be FIG JAM here just putting weight to my argument!
-
@frederik said:
I apologize on beforehand... It is not my intention to sound annoyed and also not my intention to offend anyone here, but... Trying to excuse that some users do not want to read a manual is utterly ridiculous...
If you want to learn how to use any application, it is a necessity to read a very simple manual or a couple of tutorials...I don't know anybody using i.e. Adobe PhotoShop, who haven't read through some simple manuals or tutorials to get some basic knowledge...
Trust mate I for one took no offence!
Im my own defence! Part the reason I trial software without a manual is to determine the steepness of the learning curve and that realising that of the many tools in ones arsenal some may well be used on an irregular basis.
If one can determine the workflow easily without reference it is then logical that later after they are somewhat proficient in the app and don't use it for some time chances are they wont need to relearn the process then!
And mate I can also suggest in regards to Photoshop, mate I've never read any manual and only one tut in the newsagency in a mag on how to create brushes, I've never opened the help file and once reading a thread on the pushpullbar about someone using actions to assist repetitive tasks set about learning actions myself and developed an action that day that allows me to create colour, bump and spec maps for floor and wall tiles that stops at points to allow me to adjust the grout width, depth and roughness, tile edge curve and degree or surface texture all else is done by action. Sure I have picked up little tips here and there along the way but never by searching for an answer!
About two months ago I was asked to do a book for a professional print job, I realised this would need to be done in Indesign so bought the Adobe publication Classroom in a Book. I just checked this moment and had read to page 24 of 444 before putting the book down because I realised I could learn it hands on quicker than referencing the book. The only issue that arose and called upon the help file was for the insertion of fold lines, search of the help file was unsuccessful, the book gave no hints and an online search revealed that there actually is no function for this and it needs to be done manually!
With SU I would suggest the complete opposite to all the above, I watched every video tutorial to assist my learning of the application as simply besides microsoft word it was the first program I purchased and had never used a computer before. Like TBG I've been a very late bloomer!
And don't get me wrong in Thea's case I will read the manual simply because I will likely have too, my point though is that generally I find a well designed interface and workflow can almost if not completely eliminate this need!!!
I guess I'm trying to reinforce that todays best applications are often designed so well that a user in most cases need very little reference to complete most tasks.
Advertisement