Is it possible to link SketchUp materials with IRender nXt materials and vice versa? When you render SketchUp models and scenes, you're investing a lot of time making your materials perfectly rendering. Ideally this would be needed just once, so the next time you choose the linked SketchUp material, it's automatically "mapped" to the belonging IRender nXt one. I've evaluated a couple of rendering software and so far I'm wondering why this quite obvious feature seems to be unavailable. Or am i wrong?

You need to be a member of Render Plus Software to add comments!

Join Render Plus Software

Email me when people reply –

Replies

  •  

    This is ready for you to try out. This is still a Beta feature, so there may be some problems we will have to fix.

     

    Default Materials

    IRender nXt give you the ability to define Default Materials which are saved in a Library Folder and automatically applied to SketchUp Materials placed in your model before rendering.

    • Define your rendering settings - reflection, bump maps, etc. - on the SketchUp Material
    • Save as a Default Material
    • These setting will then be used whenever you use the same SketchUp material in other drawings.

    Usage

    Default materials are saved and loaded from the More Setup Tab

    Auto-synch.png
    Default Materials Settings


    Save All from Model

    will save all materials in the current model, which been added with IRender nXt onto your disk. These are saved into the roaming App data folder, e.g. C:\Users\User_Name\AppData\Roaming\IRender\Default_Materials

    Load All into Model

    - will load the latest version of any default materials into the current model.
    Only materials with the same SketchUp Material name will be loaded.

    Auto Synch before Render

    If this is checked, then Default Material Settings will be loaded for any SketchUp materials which you have not modified with the IRender nXt Material Wizard already.
    Materials Which have already been loaded, or have been modified with the right click editor will not be loaded from defaults.

    Example

    The wall behind Susan has a SketchUp Material placed on it.

    When it is rendered, it renders normally, with no special materiel settings.

    Auto-synch1.jpg
    Rendering with normal material settings - (no reflection)


    When Auto-Synch is checked, and it is re-rendered, the Default Material settings for Stone_Marble are loaded, and it is rendered with the default reflection properties.

    Auto-synch2.jpg
    You are notified when Default Materials are loaded.


    Auto-synch3.jpg
    Rendering with default materials - not reflection of Susan and the HDRi background.
  • Al

     

    Sounds like it should work, let us know when it added,  thanks

     

    Ben

  • Rich and I discussed this and we are going to add it as a feature.

    A "Synched Materials - Load" button will load all nXt materials from a specia lsynched materials folder with the same name as the SketchUp material into your drawing.

    A "Synched Materials - Save" button will save all SketchUp materials in you model which have had nXt properties added to them to the special synched materials folder.

    A checkbox, "Auto-synch" will load the saved, synched materials into the current model - only for materials which don't have nXt material properties attached to them already - every time you start a new rendering.

  • We can also take a look at loading .nXT materials from a folder which have the same name as the SketchUp materials used. And saving any modified materials as .nXt materials to the same folder. To make a synchronization easier.

  • Hi Ben

    Take your point, I did say it was a bit of a 'workaround' rather than a solution.

    You wouldn't have to re-create it in the template file - just have the template file open in another session of sketchup at the same time. Make and apply a material in your model, when you are happy with it , copy the face, patse into the template and delete the geometry. At the end of your session resave the template file and it would be updated with all your new materials. You can even go back to old models and copy and paste previously made materials in the same way. 

    Over time your collection in the template file would be quite comprehensive. I tend to reuse materials that work well for me so adding the odd new one is not too much of a bind. 

    Interesting discussion.

    Regards

     

    Mike

     

  • mmmmm...

    Mike  all a bit roundabout  and assumes all material are created at once before you start  in reality material evolve and are added to over time. I find igenerally creat a material in model then think thats works and want to save it somewhere for future use i would then have to open the template file re-create it and resave.. Ok could work. .....can't something be made to work alongside the Nxt material library that would be much better.

    Al . Components would work ok tho can try that one.

  • Mike's idea might work by just saving components with nXt materials saved for them.

    (We probably save materials properly in Components - just not .SKM files)

    You could save one component per material, or several materials per component.

    Place the component, use the imported material, and purge ununused if desired.

    I will try it out...

  • This is more of a 'work around' than a solution but may help.

    Open a sketchup session , create a number of surfaces and apply the materials you want to use in new models.

    Edit the NXT attributes (gloss etc) fo all the materials then delete the geometry.

    Save the file as, say, 'NXT template'.

    Close the file.

    Open a new sketchup session and go to Window - Preferences.

    Click template and browse to the 'NXT template' file (or whatever you have called it.)

    Click OK and then close this file.

    Now every time you open a new Sketchup file the materials, with NXT attribute,s will be preloaded from the template file and found in the 'In Model' dropdown in the materials dialogue.

    To expand the available materials simply add them to the template file and resave.

     

    Hope this helps.

     

    Regards

     

    Mike

     

     

     

     

     

  • Has this ever been resolved?  This is key (essential) for fast working,  having to re-create a materials for every model is very time consuming.  Surely an easy solution would be to add a User library accesed in nxt as the nxt library is  (ie under sketchup tab in the image) THis could be built up over time by  the user(S)  It could be  accessed from every model if users could set the location of this,  this would also be useful so multiple users could access the same library. if multiple library could be added that would be even better. This may already be feature if it is can you tell me how to get to it.

    If not could you you tell me the best way to transfer materials between models and retain the nxt properties

     

    Cheers Ben

  • Well from a SU perspective I can understand why a 3rd party software developer can't save extra material properties in a .skm file. It could lead to a scenario where compatibility issues arise with non render users. So for now that's a given limitation of SU.

    With this limitation other mechanisms could be made to overcome the lack of a global (I mean SU model/file independant) link between SU material and render. I'm thinking of a automatic mapping mechanism based on the SketchUp material name. For that mechanism you could define a naming convention how (large) collections of SU materials are automatically mapped to their render counterpart. I'm aware of the SU behaviour automatically instancing SU materials when you import components. SU will for example create "DarkWalnutEuropean1" when "DarkWalnutEuropean" exists in the current model. So the mechanism should be intelligent enough to handle with these variations.

    It would in my opinion also very powerful when it's possible to create a global "material linking table". Every table row defines which SU material is being mapped/linked to which (existing) render material during render time. This mechanism could help gradually tie together SU and the render software, as the effort put into creating render materials cummulates during the life time of both software packages.

    Most renderer makers I've seen seem to put their effort in improving all sort of very interesting things, but not in the tight integration with the 3D modellers and material handling during lifetime. RPS is in my opinion a positive exception from SU perspective.



    Al Hart said:
    Unfortunately, when you save a SketchUp material from a SKP model, it does not save the attributes on the model, so there is no way we can find and reuse the attributes on the material which you altered.

    This is a bug in SketchUp, You can put attributes on SketchUp materials, and you can then save these materials into your own library, but SketchUp either does not save, or does not restore the attributes (I forget which)

    We could automatically create a nXt .ArMaterial material in a user library, and then automatically use it for all models which use the same SketchUp material.

    What do other users think? Should we provide a better way to save and reuse settings on SketchUp materials?

    We do now, however, have a concept of a User nXt material. If you save your material into a the user library, then you can reload and use the nXt .ArMaterial, and place it directly on a SketchUp surface.


    Manfred van der Voort said:
    Hi Al,
    Suppose I'm making a new model and use let's say as a SketchUp material "LightWoodHardMaple". This material has been used before in another model and was "enhanced" with the render/material specific attributes for reflection, bump, glossiness, etc. So far so good.
    Now I use this in another SU model. But as far as I can see the relation between the SketchUp material and the render/material attributes isn't stored somewhere. So my cocern is that for this new 3D model I have to enter the render/material specific attributes again. Does this makes sense or am I wrong?

This reply was deleted.