Results 1 to 6 of 6

Thread: ScreamerNet ideas

  1. #1

    ScreamerNet ideas

    Hi!
    I am running out of ides so if anyone have any idea what to look for it would be nice.

    I got my hands on 3 old Proliant rack servers so I set them up for screamernet rendering (LW 2015).

    All looks correct, LW see all 3 nodes and they fire away when I click on start render but....

    One of the 3 nodes do not render any files ("Unable to access the scene file"), the setup on all 3 is identical (or at least should be and there are only 2 network shares mapped to 2 drives so not much that can go wrong, but as I said, it cannot access the scene files for some reason, it is the same share as the command/config folder and it can access those so the network share should be fine, I have tried to find anything that is different between that node and the other 2 but I can't find anything.

    And yes I can access the scene file from the file explorer

    I am sure it is something silly I have done but so far I have not been able to figure out what it is.
    LightWave 2015.3 - Fantasy web comic: http://rustandmagic.se https://www.facebook.com/rustandmagic57/
    "I may not change the world but I'm gonna leave a scar" (Charlie Starr - Blackberry Smoke)

  2. #2
    I found out what the problem was, just in case someone else run into it...

    I had the content folder mapped to drive M:, and in default.lws it was set to M:

    So LW tried to render the scene from M:Scenes/myscene.lws and as long as the current directory for drive M was the root everything worked otherwise not, so changing Content Folder from M: to M:\ fixed the problem, now it renders on 3 nodes, with 64GB ram each (36 Xeon cores) pretty fast for < $500 even though the CPU's are not as fast as a modern i7.
    LightWave 2015.3 - Fantasy web comic: http://rustandmagic.se https://www.facebook.com/rustandmagic57/
    "I may not change the world but I'm gonna leave a scar" (Charlie Starr - Blackberry Smoke)

  3. #3
    Hi!
    Anyone ever had this happen ?

    I got all files setup and it works fine to use LWSN now, the only problem is that when I now click the "Switch to modeler" (F12) button in Layout it starts up 2 modelers for some reason, first it starts one with the object I had selected and then it starts another empty one, I have been comparing files and I cannot see anything wrong, and I have not changed the hub configuration, if I click "Lunch modeler" from the hub popup menu it only starts one modeler so it looks like it is some hickup with Layout, but no idea what it could be.
    LightWave 2015.3 - Fantasy web comic: http://rustandmagic.se https://www.facebook.com/rustandmagic57/
    "I may not change the world but I'm gonna leave a scar" (Charlie Starr - Blackberry Smoke)

  4. #4
    Registered User Kaptive's Avatar
    Join Date
    Jan 2006
    Location
    UK
    Posts
    776
    This happens to me 95% of the time. I also find that modeler just silently closes in the background all the time. There are some really fundamental issues going on with LW, that although they aren't scene breaking etc, they're really annoying when it is constant. These two issues combined means that modeler closes silently, so then you have to click the modeler button to reopen it and it does as you say, opens two copies with one containing the object and the other blank. I have to assume it is a hub issue of some sort.
    I also seem to have the same issue with older versions of LW, 2015 / 2018 / 2019.
    I've made an assumption that it is caused by something that lies between the hub and Windows 10. I never had these problems on Windows 7.

    Note: One additional aspect on my setup is that I have classic shell installed which I used as a transition between Win7 and 10. I don't like 10 at all, and classic shell seemed to bridge that a little. I'm not sure if this is a factor. I'd be interested to know if you have anything like this installed too? Might be a weird connected cause.... or not.
    Last edited by Kaptive; 02-13-2020 at 02:45 AM.

  5. #5
    Hi!
    I run on Windows 10 and I don't use the classic shell, it took some time but I finally got used to Windows 10

    It never happend before I setup network rending so I would think it has something to do with that, but at least it's interesting to know that it has happened to others also.
    LightWave 2015.3 - Fantasy web comic: http://rustandmagic.se https://www.facebook.com/rustandmagic57/
    "I may not change the world but I'm gonna leave a scar" (Charlie Starr - Blackberry Smoke)

  6. #6
    Registered User Slartibartfast's Avatar
    Join Date
    Jun 2012
    Location
    Sweden
    Posts
    420
    I also have this problem since a while ago. Using Win 10 & 2015.3, but I think it worked in earlier versions of Win 10. Really annoying. All my computers show same behaviour ;-)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •