awesome release 4.1! well done Henrik and the rest of the team.
I'm opening up a thread regarding what I would love to see in the next realeases although those features might be more oriented towards the industry I am in (entertainment - movie vfx and also videgames) The interest in our community is growing so I hope to see those additions soon!?
1- subdivision surfaces (cannot do without this).
2- displacement maps (both regular and vector) This is also a must to use in combination with the subd instead of rendering millions of straight polys which is not always practical and efficient.
3- support for multiple UV tiles (and not only 0-1) We use this basically for every asset to maximize texture resolution. A full character/creature might require up to 40-60 tiles (2k or 4k) if not more.
4- the ability to layer up things in the shaders and therefore more flexibility to the more advanced users
5- support for rendering hair/fur
6- support for Ptex format for textures
please feel free to add more to the list
cheers,
Marco
I'll add one for the technical illustrators among us:
- a transparency slider for the Toon material. Instead of having to use solid opacity maps with various gray scales to get the desired 'ghosting'. Too cumbersome for quick see-throughs.
Dries
When you go to add a folder to the libraries let's have a 'Browse' button to navigate to the relevant folder
QuoteI'll add one for the technical illustrators among us:
a transparency slider for the Toon material. Instead of having to use solid opacity maps with various gray scales to get the desired 'ghosting'. Too cumbersome for quick see-throughs.
Dries
+1
Also this:
---
scenario:
I work in my file and I have some hidden elements.
I isolate one element of my scene for export by:. obj
I would now like to return to the state of visibility before the isolation of the element to continue my work.
Currently it is impossible.
---
my best wish!!!! :P
http://keyshot.com/forum/index.php/topic,3934.0.html
free displacment elements into the scene:
http://keyshot.com/forum/index.php/topic,6048.0.html
dynamic free quides lines:
http://keyshot.com/forum/index.php/topic,5713.0.html
i want the "dong"!!!!!:
http://keyshot.com/forum/index.php/topic,2474.15.html
garden:
http://keyshot.com/forum/index.php/topic,4256.0.html
i want many tree!!!! :
http://keyshot.com/forum/index.php/topic,5282.0.html
a template more visual please:
http://keyshot.com/forum/index.php/topic,3540.0.html
http://keyshot.com/forum/index.php/topic,4647.0.html
a blur effect for a selected material only:
http://keyshot.com/forum/index.php/topic,4578.0.html
led:
http://keyshot.com/forum/index.php/topic,2501.0.html
log for settings memory:
http://keyshot.com/forum/index.php/topic,4367.0.html
cast or not cast shadows:
http://keyshot.com/forum/index.php/topic,4055.0.html
lock animation:
http://keyshot.com/forum/index.php/topic,3360.0.html
Thank you.
Antoine
@evilmaul - 7. rename KeyShot to Maya.
Sorry, couldn't resist. ;-) We will look into these things, balancing advanced features with the core values of KeyShot: easy, fast, accurate.
thanks Thomas and yes keep those core values for sure!
PS: KS as an alternative maya renderer would kick ass and send home vray and arnold. :)
Yep- stick to the core values! Please, no bloatware!
"Display States" would be very useful for large assemblies- this could tie in with view sets? Similar to what SolidWorks has now, which makes toggling between stuff very quick and easy. This assembly > that assembly, etc.
Bill G
Quote from: Speedster on June 27, 2013, 04:21:34 PM
....
"Display States" would be very useful for large assemblies- this could tie in with view sets? Similar to what SolidWorks has now, which makes toggling between stuff very quick and easy. This assembly > that assembly, etc.
Bill G
+1
And yes, first of all congrats on 4.1, more than awesome!
Therefore it feels a little strange asking for the next thing already..! ;)
There's a few things I would like to see further improvement on, a few which i'm sure you are already working on.
- The procedurals are awesome, and I know more will be added.
Personally I'ld like to see a scratches one, and 'spangle' (glavanised steel, MDF/OSB, etc.)
- Procedurals in the opacity channel
- Option for two point perspective in addition to true perspective and orthographic
- Wider support for dragging and dropping colour chips. (for example between colour 1 and colour 2 seen on many procedurals)
- Speaking of colour chips, maybe a third chip in some of the procedurals?
- Wider use real world values, or make it clearer what the units are (i.e. dolly is indicated in mm if that is the modeling unit) inclination is in degree etc)
- Not nessisarily asking for layers, but if we would have two texture slots per channel (maybe thats just layers by another name ;) ) it would greatly expand the material variation and flexibility.
- Sun-Sky system?
N
And "KeySmell" for that added realism!
Bill G
For me, the next best thing would be "photo background match" with all 3 axis. That be a BIG step forward, as was the "ground material texture".
Obviously this request is only a 1% compared to my request to get off of f*#-! Windows XP with its memory limit >:( >:( >:(
How long still must I ask IT here for that ... pffffffffffffffrt !
QuoteFor me, the next best thing would be "photo background match" with all 3 axis.
+2
"invert" option with the Opacity map, might be handy for when you got the black/white wrong in PS, or for other reasons ... ?
PhilippeV8: There is an "Inverse Color" on opacity maps now?
"now" as in KS4.1 ?
If so ... OK THAN ! ;D That was quick :D
Expect IT to give me an install of KS4.1 within the next ... say ... 6 months ... those guys are SO buzzy ... they got to chat and chat for 30min at least with everyone :P ::)
It has been there since opacity maps was introduced.
oeps ... :-[
mental note: must read manual on each new version
... check !
I had no idea !
No problem - now you learned something new today ;)
Yes ! FINALY ! :p It's 15:21h here ... I'm early on the learning today :D
You can go home now. Your day is complete ;-)
Actually ... NOW it is ;)
First must go get the boys tho 8)
QuoteObviously this request is only a 1% compared to my request to get off of f*#-! Windows XP with its memory limit >:( >:( >:(
How long still must I ask IT here for that ... pffffffffffffffrt !
When I was on XP, renders (if I could even open them) would take 4-12 hours each, and SolidWorks ran like molasses. Switched to Win7x64, kicked it to 16 GB of RAM and went to dual quad-cores, for 8 cpu's. A 4 hour render now runs about 6 minutes. And SW is a blazing rocket!
IT has to understand that your time is money- a new box and/or OS would likely recoup in weeks. That's an ROI that works!
Bill G
I am under the impression that IT doesn't care at all about my productivity ..
Also, they did some tests with updated OS and Inventor and noticed that it doesn't help much and found out for Inventor it gains more from different approach to using the parametric drawings.
So they don't even botter testing if it does change much for my case.
Also they always bla bla a lot 'bout things I don't understand and in the end I don't understand why I can't just simply get Win7 on the render PC.
Quote from: DriesV on June 28, 2013, 12:42:31 PM
those IT rednecks...
Hey - I resemble those remarks. And it's "redneck geek" to you, buddy! ;D
I'm amazed how far behind your IT is PhilippeV8. We may have went to Win7 2 years ago, bought our 20 artists HP Z800s with dual 6 cores (needed an excuse to get one for myself), and now we are working on a dedicated render farm - but we still like to talk about things no one understands. (Not even myself most of the time)
I should stay home from work on monday ... then when they call, I'll say I'm not going untill they put W7 on the render pc. ;D
I would love you guys to stay within the topic of the thread please.
Keep on adding what you wish to see in the next KS releases. Perhaps we could do a poll (other softwares have that as well and ppl vote for specific features they would like to see implementes and those which get more votes move forwards on top of the wish list)
For me , of those features that I listed, I would give priority to have geometry rendered as Subd (have just an attrib turned on by the user per geo or hierarchy of objs) and support for displacement maps.
cheers,
Marco
I've posted about this before, but will bring it up again. I can't stand how you can't select a part unless you're in the Scene Tree tab.
And why is Unlink materials in the right click context menu but Link isn't?
I also think that the primitives should be in the menu instead of having to go to Import, navigate to the KeyShot models folder and then select your primitive of choice.
Lastly, the resolution limit on the standard edition. I think for a thousand dollar rendering software, I should be able to render an 8 1/2 x 11 image at print resolution.
You can select parts in the realtime window, and using shift + left mouse button drag you can multi select. The parts won't highlight, only if you are in the scene tree.
Linking/Unlinking:
Unlink works on a single part or multiple parts. Link requires additional UI. You link by copying and pasting a material from on part to the other or multiple.
Import - I guess we can add that, just like you can add a ground plane from the menu.
As far as resolution goes, I assume you mean 300dpi by print resolution. Correct, you will only get about 1/2 a page with the standard version.
How about that "Frontplate with transparency from the alpha chanel tiff" type of wishlist-entry ? :)
For parts of the backplate that need to overlapse the rendered scene or objects.
1. Bokeh DOF - Maybe using the gpu to save processor power, like you did for bloom and vignetting?
2. Lens Aberration
3. Different camera lenses, Ex. Fish eye
4. (Easy one) - Dark gray interface, in some scenes the interface is so distracting and luminous, that is hard to focus on the scene.
5. Bokeh DOF :P