Results 1 to 11 of 11

Thread: Linux support?

  1. #1
    Registered User
    Join Date
    Jan 2018
    Location
    Poland
    Posts
    13

    Linux support?

    Hi,
    I'm pretty sure nobody will know for sure, but do you thing there is any potential chance that there will be a native Linux version of Lightwave?

    After many years of having Apple-based systems, right now I'm in the middle of moving to Linux. I really like LW, and while the new Blender seems like a great alternative, I really would prefer to keep using LW. It does not work in VirtualBox (AFAIK) and there are (were?) problems with activation in Wine. Also, apart from C4D, all major software has Linux versions. Maybe, if there are more peaople interested, we could put some pressure on on NewTek (or whoever owns the LW now) on the Linux version? Apple will not support OpenGL soon, so key elements of LW will have to be rewritten as well.

    What is your opinion?
    Adam

  2. #2

    I'm currently looking into a render farm option, and Linux could be of interest. [Free]

    I'll have to check current price of Win7. Looking at 6-8 machines.

    But looking at Linux vs GPU render, definitely GPU render support is of much higher interest I must say.
    LW vidz   DPont donate   LightWiki   RHiggit   IKBooster   My vidz

  3. #3
    Founding member raymondtrace's Avatar
    Join Date
    May 2003
    Location
    Ohio
    Posts
    970
    Quote Originally Posted by AdamWysokinski View Post
    ...Maybe, if there are more peaople interested, we could put some pressure on on NewTek (or whoever owns the LW now) on the Linux version?...
    "Pressure" is simply put on by filing a feature request. Prioritization of development effort is placed on quality and quantity of requests.

    As LightWave has worked fine in Wine (discovery mode only) for at least a decade, I'm assuming there's some fundamentally unworkable issue with porting the licensing mechanism. Otherwise, the move would seem too easy and too obvious.
    LW7.5D, 2015, 2018, 2019 running portably on a USB drive on an Amiga 2500 running Wine.

  4. #4
    Super Member Kryslin's Avatar
    Join Date
    Feb 2009
    Location
    Prescott, IA
    Posts
    1,537
    From what I remember on the subject, the problem lies in the Sentinel Licensing system, not with Lightwave. At least, with LW 9.6, which still relied on the dongle.
    --------
    My Scripts for Lightwave
    Intel Core i7 960 @3.20 Ghz, 24 GB ram, EVGA 6GB GTX980Ti "Classified" driving 2 x HP LA2405.

  5. #5
    Super Member
    Join Date
    Sep 2003
    Location
    Barcelona
    Posts
    1,695
    HI,
    I have a virtual machine (KVM) set-up to boot Windows 10 pro from a Linux Host. Configuring the VFIO (intel_iommu, etc...) the system boots dedicating a GPU (or more) to the Guest VM. Then I have assigned a separate keyboard and the Wacom to the config of the VM so when it launches it has its own keyboard and tablet (they work as usual when not starting the VM, unlike the GPU(s) assigned to the VM.) I have a multimonitor workstation, so I plug the monitors also to the card dedicated to the VM, so I can use them in both. I can disable the iommu part, reboot and get the dedicacted to the VM GPU back on Linux if needed.

    This way, I can have full windows gpu acceleration, licensing etc... for LightWave/Octane and the Affinity suite of software without having to leave Linux and reboot back and forth. For long or big projects I also have a partition with Windows so I can use all system resources.

    Setting up the Linux system this way can be a bit confusing at first, but it's really a matter of following well explained directions, step-by-step. To me it's well worth the effort, once it's working my workflow improved quite a bit.

    PS: I can also assing more or les RAM and CPU cores to each VM's boot depending on the project's needs. With a beefier new system I presume I wouldn't boot to a Windows partition again.
    Last edited by allabulle; 11-03-2019 at 06:36 AM.
    Salut!,
    Allabulle.

  6. #6

    i found Win7 is pretty cheap, so going with that if i create the farm.

    but you guys really should check out LightForge    https://render.lightforge.cc



    https://forums.newtek.com/showthread.php/161011
    Last edited by erikals; 11-03-2019 at 06:47 AM.
    LW vidz   DPont donate   LightWiki   RHiggit   IKBooster   My vidz

  7. #7
    Super Member CaptainMarlowe's Avatar
    Join Date
    May 2007
    Location
    Belfort, France
    Posts
    1,854
    I would also welcome a Linux version, if not fully native at least with the winetrick, provided NT would find a fix for the licensing system.
    My next rig will most certainly be AMD & Linux Mint based.

  8. #8
    Registered User
    Join Date
    Jun 2014
    Location
    Right here
    Posts
    1,653
    Quote Originally Posted by erikals View Post
    i found Win7 is pretty cheap, so going with that if i create the farm.
    If its a server farm for yourself (which is offline) that's fine but I hope you're not planning to provide web services based on Win7 that will not get future security patches next year.

  9. #9

    no, all offline.    
    LW vidz   DPont donate   LightWiki   RHiggit   IKBooster   My vidz

  10. #10
    Registered User
    Join Date
    Jun 2014
    Location
    Right here
    Posts
    1,653
    Quote Originally Posted by AdamWysokinski View Post
    Hi,
    I'm pretty sure nobody will know for sure, but do you thing there is any potential chance that there will be a native Linux version of Lightwave?
    Would be a great move indeed but imho not realistic for LightWave as there are plenty of areas that need much work on the application itself.

  11. #11
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,691
    Once LW's solely using Qt for UI, and no longer has nearly as much tightly-bound, platform-dependent input/UI toolkit code, a Linux port could be much more attainable. Hopefully, as the devs deal with the Qt migration, they're also isolating and adding abstractions at the relevant platform-dependent seams, etc.

    Unfortunately, that's still a ways off in the future. Attempting a port before the shift to Qt is done would be an exercise in futility. The existing input infrastructure and UI toolkit LW code are much too tightly-bound and specialized for the existing platforms (Win & Mac). Platform-decoupling and migrating the existing input and UI toolkit code to Linux would nigh-certainly require substantially more effort than migrating the existing platforms to use Qt instead of that code. Further, completion of migration to Qt would still need to occur, relegating effort spent migrating earlier input/UI toolkit code as wasted effort.
    Last edited by jwiede; 11-03-2019 at 06:56 PM.
    John W.
    LW2015.3UB/2019.1.4 on MacPro(12C/24T/10.13.6),64GB RAM, NV 980ti

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
  •