Daz Studio and Linux

1151618202154

Comments

  • mambanegramambanegra Posts: 580

    Virtual box offers a nice, free VM system that runs Windows just fine. If your tools don't require direct X or advanced rendering stuff, it probably would do just fine. I have a few coworkers that run Linux as their main OS with Windows as VM for using Office (when sharing documents with edit tracking with windows only people, you have no choice)

  • mambanegramambanegra Posts: 580
    AllenArt said:

    Might be a Pro and Enterprise only feature.

    Laurie

    At this point, it's only available if you're running a Windows Insider preview that supports it.

    regardless, it's useless if you can't SSH into the thing. At least to me, since my machine is headless. I am NOT going to type into a VNC displayed terminal, lol. 

  • kyoto kidkyoto kid Posts: 41,023

    Windows 10 has a new Ubuntu subsystem that allows native Linux programs to run in Windows 10.  Canonical/Ubuntu sold out.

    Kendall

    ...yeah but it still means having W10 which is a no go for me.

  • Kendall SearsKendall Sears Posts: 2,995

    DirectX in virtualbox works just fine.  OpenGL is a bit more shaky.  DS in Virtualbox has some real problems due to some methods DAZ uses to keep the Viewport active.  Due to the way VB forwards the OpenGL calls it ends up that the DS viewport stays ON TOP OF EVERYTHING and doesn't like to move or update.  This is a rather new problem that started in 4.8+

    Kendall

  • Kendall SearsKendall Sears Posts: 2,995
    AllenArt said:

    Might be a Pro and Enterprise only feature.

    Laurie

    At this point, it's only available if you're running a Windows Insider preview that supports it.

    regardless, it's useless if you can't SSH into the thing. At least to me, since my machine is headless. I am NOT going to type into a VNC displayed terminal, lol. 

    To be pedantic, Windows prefers RDP over VNC.  VNC works, but is significantly less efficient in a Windows environment.

    Kendall

  • Azure_ZeroAzure_Zero Posts: 65

    Windows 10 has a new Ubuntu subsystem that allows native Linux programs to run in Windows 10.  Canonical/Ubuntu sold out.

    Kendall

    Canonical/Ubuntu did not do a sell out willingly, more like they were bullied by Microsoft to give them what they wanted.

  • Windows 10 has a new Ubuntu subsystem that allows native Linux programs to run in Windows 10.  Canonical/Ubuntu sold out.

    Kendall

    Canonical/Ubuntu did not do a sell out willingly, more like they were bullied by Microsoft to give them what they wanted.

    I doubt they "sold out" as Ubuntu is Open Source.

  • mambanegramambanegra Posts: 580
    AllenArt said:

    Might be a Pro and Enterprise only feature.

    Laurie

    At this point, it's only available if you're running a Windows Insider preview that supports it.

    regardless, it's useless if you can't SSH into the thing. At least to me, since my machine is headless. I am NOT going to type into a VNC displayed terminal, lol. 

    To be pedantic, Windows prefers RDP over VNC.  VNC works, but is significantly less efficient in a Windows environment.

    Kendall

    Yeah, except my computer came with Windows 10 Home, which doesn't allow RDP for some silly reason. VNC pretty much sucks, but I still have DS on my mac to generate the scenes, so the lousy mouse tracking in DS over VNC isn't too much of a PITA. 

  • Kendall SearsKendall Sears Posts: 2,995
    edited July 2016

    Windows 10 has a new Ubuntu subsystem that allows native Linux programs to run in Windows 10.  Canonical/Ubuntu sold out.

    Kendall

    Canonical/Ubuntu did not do a sell out willingly, more like they were bullied by Microsoft to give them what they wanted.

    I doubt they "sold out" as Ubuntu is Open Source.

    Linux is open source. Ubuntu is a specific distro controlled by Canonical, just as Fedora and RHEL are controlled by RedHat.  The individual contents of the distros are (mostly) Open Source, but the included pieces inside are specific to Canonical/RedHat/Oracle's whims.  Just as Canonical created and controlled (and pushed) their own desktop/working environment they decided to sell their unique versions of Linux to MicroSoft for hosting in Windows 10.

    They weren't bullied, an offer was made and Canonical accepted it.  Shuttleworth et al have always been known to "go for the pound" where it is possible.  In general, I have no problem with this as a Free Market Capitalist myself.

    Kendall

    Post edited by Kendall Sears on
  • GafftheHorseGafftheHorse Posts: 567

    Hi

    Just been using Daz3d on Archlinux for the last week. 32bit Daz only up to now. Apart from the CMS issue, and issues with more complex scenes which I have gotten around by using the native 3Delight renderer.

    I've gotten the 64bit installed by picking manual install off the daz3d download page, and using the instructions on the wine setup mork left.

    Is there a dim x64? as I can't find it on the d/l page and daz3d keeps feeding me the 32bit one on d/l requests. I could copy the content from the 32bit version over from my daz32 wine prefix, but that's not a great solution going forward...

    Regards

    Jeff

  • Kendall SearsKendall Sears Posts: 2,995
    jefftees said:

    Hi

    Just been using Daz3d on Archlinux for the last week. 32bit Daz only up to now. Apart from the CMS issue, and issues with more complex scenes which I have gotten around by using the native 3Delight renderer.

    I've gotten the 64bit installed by picking manual install off the daz3d download page, and using the instructions on the wine setup mork left.

    Is there a dim x64? as I can't find it on the d/l page and daz3d keeps feeding me the 32bit one on d/l requests. I could copy the content from the 32bit version over from my daz32 wine prefix, but that's not a great solution going forward...

    Regards

    Jeff

    DS 32-bit has been working pretty well for some time in WINE.  DS 64-bit has... shall we say, some difficulties.  Some of this is inherent weaknesses in the code of WINE, where fixes are predicated on the motivations of the volunteers who make the fixes.  Programs that have lots of volunteers among the WINE group get lots of fixes quickly, while lesser used programs like DS get the benefits of the fixes that happen to overlap.  It is a sad fact that DirectX is the WIndows favorite and that OpenGL under Windows64 is woefully supported (and grudginly so at that).

    What it will take is someone who uses DS64 to take on the job of finding those routines that cause DS to choke and either find someone to fix them or fix the problem themselves and submit the fixes.  I have long since lost the time to devote to DS64 under WINE.

    Kendall

  • KeryaKerya Posts: 10,943
    jefftees said:
    ...

    Is there a dim x64? as I can't find it on the d/l page and daz3d keeps feeding me the 32bit one on d/l requests. I could copy the content from the 32bit version over from my daz32 wine prefix, but that's not a great solution going forward...

    ...

     

    DIM is 32bit only.

  • GafftheHorseGafftheHorse Posts: 567
    Kerya said:
    jefftees said:
    ...

    Is there a dim x64? as I can't find it on the d/l page and daz3d keeps feeding me the 32bit one on d/l requests. I could copy the content from the 32bit version over from my daz32 wine prefix, but that's not a great solution going forward...

    ...

     

    DIM is 32bit only.

    Ah, that would explain it. Thank you.

    Hi

    jefftees said:

    Just been using Daz3d on Archlinux for the last week. 32bit Daz only up to now. Apart from the CMS issue, and issues with more complex scenes which I have gotten around by using the native 3Delight renderer.

    I've gotten the 64bit installed by picking manual install off the daz3d download page, and using the instructions on the wine setup mork left.

    Is there a dim x64? as I can't find it on the d/l page and daz3d keeps feeding me the 32bit one on d/l requests. I could copy the content from the 32bit version over from my daz32 wine prefix, but that's not a great solution going forward...

    Regards

    Jeff

    DS 32-bit has been working pretty well for some time in WINE.  DS 64-bit has... shall we say, some difficulties.  Some of this is inherent weaknesses in the code of WINE, where fixes are predicated on the motivations of the volunteers who make the fixes.  Programs that have lots of volunteers among the WINE group get lots of fixes quickly, while lesser used programs like DS get the benefits of the fixes that happen to overlap.  It is a sad fact that DirectX is the WIndows favorite and that OpenGL under Windows64 is woefully supported (and grudginly so at that).

    What it will take is someone who uses DS64 to take on the job of finding those routines that cause DS to choke and either find someone to fix them or fix the problem themselves and submit the fixes.  I have long since lost the time to devote to DS64 under WINE.

    Kendall

    As an Archlinux user, I am fairly conversant with Linux, just never had the inclination to use Wine before I discovered Daz3d, and I am totally out of touch with windows as I've not used it much since 2000. I will see what I can figure out though.

    Thank you both for your quick replies.

  • GumpOtakuGumpOtaku Posts: 106

    If it be of any help to anyone, I went to WineHQ and found a successful test of DS4.9. 64bit on Fedora:

    https://appdb.winehq.org/objectManager.php?sClass=version&iId=33385

    Meanwhile, I am trying to figure out how to get this working on Mint 18.

    ~GO :D

  • Kendall SearsKendall Sears Posts: 2,995
    GumpOtaku said:

    If it be of any help to anyone, I went to WineHQ and found a successful test of DS4.9. 64bit on Fedora:

    https://appdb.winehq.org/objectManager.php?sClass=version&iId=33385

    Meanwhile, I am trying to figure out how to get this working on Mint 18.

    ~GO :D

    That report was from February.  In the various threads here, there have been sporadic reports of "working" and then subsequent "not working" reports.  Your mileage may vary depending on the distro, the wine version, the phase of the moon, etc.   Results, either way, put here can help people get around issues and maybe finally come up with a stable set of instructions to get DS64 working.

    Kendall

  • GumpOtakuGumpOtaku Posts: 106

    Hi Kendall, 

    My latest attempt yeided the following error message:

    DAZStudio.exe caused UNKNOWN_ERROR in module "C:\windows\system32\KERNEL32.dll" at 0033:000000007B84C5E7

    This is an improvment for me, as i don't go this far before Wine 1.8 shutting me down

    ~GO :D

  • KnittingmommyKnittingmommy Posts: 8,191
    GumpOtaku said:

    If it be of any help to anyone, I went to WineHQ and found a successful test of DS4.9. 64bit on Fedora:

    https://appdb.winehq.org/objectManager.php?sClass=version&iId=33385

    Meanwhile, I am trying to figure out how to get this working on Mint 18.

    ~GO :D

    This should be totally doable as I managed to get DAZ 4.9 up and working with Mint 17 without Connect.  I did get DIM up and running, but with manual downloads and installing with DIM after downloading packages myself.  I never got that error, though, so I don't know what caused that.

  • GumpOtakuGumpOtaku Posts: 106
    edited July 2016
    GumpOtaku said:

    If it be of any help to anyone, I went to WineHQ and found a successful test of DS4.9. 64bit on Fedora:

    https://appdb.winehq.org/objectManager.php?sClass=version&iId=33385

    Meanwhile, I am trying to figure out how to get this working on Mint 18.

    ~GO :D

    This should be totally doable as I managed to get DAZ 4.9 up and working with Mint 17 without Connect.  I did get DIM up and running, but with manual downloads and installing with DIM after downloading packages myself.  I never got that error, though, so I don't know what caused that.

    I have monitored your experiments for a few days and loved your first Irsy render on Mint 17. Do you mind me asking how you got ds to work in Mint 17? DIM fully working is opinional, but I know how to unzip and arrange,

    ~GO :D

    Post edited by GumpOtaku on
  • KnittingmommyKnittingmommy Posts: 8,191

    I basically followed these instructions from Cup of Linux with a couple of modifications.  The first being I went ahead and tried installing the 64 bit version because I wanted to use Iray even though the instructions say it won't work and are for the 32 bit version.  I did not install the dotnet stuff because Wine couldn't find it for whatever reason and didn't install any of those packages.  So, basically, I just installed the following packages: vcrun2005; vcrun2010; tahoma; d3dx9; and I believe I installed the corefonts, but I'm not absolutely sure about that.  I, also, made sure I was using the absolute latest version of Wine, as well as Play on Linux, and I made sure I was using the latest version of Mint 17.  I'm also running a machine with an AMD FX 8350 and a Radeon R7 460X so I'm using the FGLRX driver for my graphics.  I think one of the major differences is that my version of Play on Linux and Wine were newer than what the person who wrote the tutorial used.  The 64 bit version installed fine this time whereas the last time I tried installing with the previous version of Wine, I never did get that up and running.

    Unfortunately, in a totally unrelated issue, I managed to totally destroy my install of Linux trying to get Tomb Raider working on it and thoroughly messed up all of my graphics and lost the GUI.  I fixed that and now I can't log into Linux because I don't think it remembers my password and all of my attempts to reset the password to a new one won't work so I haven't been able to get into Linux since I managed to get DS up and running.  I'm trying to fix all that without totally reinstalling Linux.  I'm hoping to get that fixed this week.  We'll see if I'm smart enough to get that figured out.  Sigh.  I have a feeling I should have stopped while I was ahead.

  • Kendall SearsKendall Sears Posts: 2,995

    I basically followed these instructions from Cup of Linux with a couple of modifications.  The first being I went ahead and tried installing the 64 bit version because I wanted to use Iray even though the instructions say it won't work and are for the 32 bit version.  I did not install the dotnet stuff because Wine couldn't find it for whatever reason and didn't install any of those packages.  So, basically, I just installed the following packages: vcrun2005; vcrun2010; tahoma; d3dx9; and I believe I installed the corefonts, but I'm not absolutely sure about that.  I, also, made sure I was using the absolute latest version of Wine, as well as Play on Linux, and I made sure I was using the latest version of Mint 17.  I'm also running a machine with an AMD FX 8350 and a Radeon R7 460X so I'm using the FGLRX driver for my graphics.  I think one of the major differences is that my version of Play on Linux and Wine were newer than what the person who wrote the tutorial used.  The 64 bit version installed fine this time whereas the last time I tried installing with the previous version of Wine, I never did get that up and running.

    Unfortunately, in a totally unrelated issue, I managed to totally destroy my install of Linux trying to get Tomb Raider working on it and thoroughly messed up all of my graphics and lost the GUI.  I fixed that and now I can't log into Linux because I don't think it remembers my password and all of my attempts to reset the password to a new one won't work so I haven't been able to get into Linux since I managed to get DS up and running.  I'm trying to fix all that without totally reinstalling Linux.  I'm hoping to get that fixed this week.  We'll see if I'm smart enough to get that figured out.  Sigh.  I have a feeling I should have stopped while I was ahead.

    To get in to change your password is not hard:

    1) When booting, interrupt the GRUB countdown.

    2) "edit" the boot sequence (the keystrokes may be slightly different depending on your distro)

    3) find the line that starts with 'linux /vmlinuz-4.x.x-xxx.....' and add the word 'single' to the end.

    4) fress F10 to boot from the changes (or whatever keystroke yours requires if different)

    you should be dropped to a simple # prompt.  here use the 'passwd' command to change the password.

    # passwd myuser

    press Control-D and reboot the machine into full startup

    Kendall

  • KnittingmommyKnittingmommy Posts: 8,191

    I found instructions similar to this and tried it, but even after changing the password, it didn't seem to take.  I can type in the new password, but it changes the screen like it's thinking and then just goes back to the log on screen.  I don't even get a 'that's the wrong password' or anything.  However, your instructions are slightly different so I'll give it a try later when DS is finished with it's current render and I can get out of Windows.  I'll let you know if it works.  If not, I think my problem isn't that it doesn't know the password, but that I can't set one and it's just doing nothing but spinning it's wheels.

  • Kendall SearsKendall Sears Posts: 2,995
    edited July 2016

    I found instructions similar to this and tried it, but even after changing the password, it didn't seem to take.  I can type in the new password, but it changes the screen like it's thinking and then just goes back to the log on screen.  I don't even get a 'that's the wrong password' or anything.  However, your instructions are slightly different so I'll give it a try later when DS is finished with it's current render and I can get out of Windows.  I'll let you know if it works.  If not, I think my problem isn't that it doesn't know the password, but that I can't set one and it's just doing nothing but spinning it's wheels.

    You've got a different problem.  It isn't your password.  You've blown out the settings for your desktop environment.  The easiest way to get around this is to change the DE upon startup.  If you're using the GDM login manager (or LDM) there should be a "gear" icon next to the Affirmative button on the password entry.  Click on the gear and select a different Session Type.  That may get you in.  If it still doesn't then you've likely also blown away your video card's config as well.  That's a different type of fish.

    EDIT:  You can also set up a new user, log in to that to get a GUI, then play with the settings until you get the original working.

    Kendall

    Post edited by Kendall Sears on
  • mambanegramambanegra Posts: 580

    I found instructions similar to this and tried it, but even after changing the password, it didn't seem to take.  I can type in the new password, but it changes the screen like it's thinking and then just goes back to the log on screen.  I don't even get a 'that's the wrong password' or anything.  However, your instructions are slightly different so I'll give it a try later when DS is finished with it's current render and I can get out of Windows.  I'll let you know if it works.  If not, I think my problem isn't that it doesn't know the password, but that I can't set one and it's just doing nothing but spinning it's wheels.

    You've got a different problem.  It isn't your password.  You've blown out the settings for your desktop environment.  The easiest way to get around this is to change the DE upon startup.  If you're using the GDM login manager (or LDM) there should be a "gear" icon next to the Affirmative button on the password entry.  Click on the gear and select a different Session Type.  That may get you in.  If it still doesn't then you've likely also blown away your video card's config as well.  That's a different type of fish.

    EDIT:  You can also set up a new user, log in to that to get a GUI, then play with the settings until you get the original working.

    Kendall

    can you ssh into the system? If so, you can probably move a few files from your home directory into a temporary subdirectory. I'm not sure which, since I am not terribly familiar with current graphical desktops, but kendall might have some suggestions. 

  • KnittingmommyKnittingmommy Posts: 8,191

    I'll try that out your suggestions and let you know if anything worked.  Thanks for the suggestions.  I really appreciate them.

  • GumpOtakuGumpOtaku Posts: 106

    I basically followed these instructions from Cup of Linux with a couple of modifications.  The first being I went ahead and tried installing the 64 bit version because I wanted to use Iray even though the instructions say it won't work and are for the 32 bit version.  I did not install the dotnet stuff because Wine couldn't find it for whatever reason and didn't install any of those packages.  So, basically, I just installed the following packages: vcrun2005; vcrun2010; tahoma; d3dx9; and I believe I installed the corefonts, but I'm not absolutely sure about that.  I, also, made sure I was using the absolute latest version of Wine, as well as Play on Linux, and I made sure I was using the latest version of Mint 17.  I'm also running a machine with an AMD FX 8350 and a Radeon R7 460X so I'm using the FGLRX driver for my graphics.  I think one of the major differences is that my version of Play on Linux and Wine were newer than what the person who wrote the tutorial used.  The 64 bit version installed fine this time whereas the last time I tried installing with the previous version of Wine, I never did get that up and running.

    Unfortunately, in a totally unrelated issue, I managed to totally destroy my install of Linux trying to get Tomb Raider working on it and thoroughly messed up all of my graphics and lost the GUI.  I fixed that and now I can't log into Linux because I don't think it remembers my password and all of my attempts to reset the password to a new one won't work so I haven't been able to get into Linux since I managed to get DS up and running.  I'm trying to fix all that without totally reinstalling Linux.  I'm hoping to get that fixed this week.  We'll see if I'm smart enough to get that figured out.  Sigh.  I have a feeling I should have stopped while I was ahead.

    I followed the tutorial and your modifications to the tee, and still went nowhere. and I'm on a freaking GTX 750 for crying out loud!!!

    ~GO :D

  • Silver DolphinSilver Dolphin Posts: 1,606

    ReactOS is an interesting Opensource project which may be able to run Daz Studio when the developers get it out of Beta> that is if it does not fall to MS. It may be what we end up using to run Daz Studio in the future if MS does go subscription like Adobe. That is if DAZ does not expand its market and create a Linux branch of it great software hint hint.I bought Adobe CS 6 and I believe I will never update again. If GIMP ever gets 64bit> I will probably change over to GIMP completely. I did this with Office, I changed to LiberOffice because MS Office is too expensive and I hate greed. I think it makes people crazy and ruins good things. I like Photoshop but it was always too expensive. I'm glad Opensource >GIMP and Blender and LiberOffice are there for those of us who cannot affort to spend so much on software. I believe Opensource is here to stay but the industry is fighting it tooth and nail becuase they don't like not having complete control over everything. In American History we called these things Monopolies, and we created laws to break them up. I believe that is why Opensource is so great it keeps Monopoly in check. So this is me saying thank you to Opensource delvopers. I would also encourage everyone to donate to Opensource from time to time to keep it alive and free for everyone.

  • KnittingmommyKnittingmommy Posts: 8,191
    GumpOtaku said:

    I basically followed these instructions from Cup of Linux with a couple of modifications.  The first being I went ahead and tried installing the 64 bit version because I wanted to use Iray even though the instructions say it won't work and are for the 32 bit version.  I did not install the dotnet stuff because Wine couldn't find it for whatever reason and didn't install any of those packages.  So, basically, I just installed the following packages: vcrun2005; vcrun2010; tahoma; d3dx9; and I believe I installed the corefonts, but I'm not absolutely sure about that.  I, also, made sure I was using the absolute latest version of Wine, as well as Play on Linux, and I made sure I was using the latest version of Mint 17.  I'm also running a machine with an AMD FX 8350 and a Radeon R7 460X so I'm using the FGLRX driver for my graphics.  I think one of the major differences is that my version of Play on Linux and Wine were newer than what the person who wrote the tutorial used.  The 64 bit version installed fine this time whereas the last time I tried installing with the previous version of Wine, I never did get that up and running.

    Unfortunately, in a totally unrelated issue, I managed to totally destroy my install of Linux trying to get Tomb Raider working on it and thoroughly messed up all of my graphics and lost the GUI.  I fixed that and now I can't log into Linux because I don't think it remembers my password and all of my attempts to reset the password to a new one won't work so I haven't been able to get into Linux since I managed to get DS up and running.  I'm trying to fix all that without totally reinstalling Linux.  I'm hoping to get that fixed this week.  We'll see if I'm smart enough to get that figured out.  Sigh.  I have a feeling I should have stopped while I was ahead.

    I followed the tutorial and your modifications to the tee, and still went nowhere. and I'm on a freaking GTX 750 for crying out loud!!!

    ~GO :D

    Sorry, I don't know what to tell you.  I'm not familiar enough with the different graphic cards to really know how they differ.  I can just go by what worked for me.  I'm still trying to get my feet wet with with learning how to do things on my own without running to my husband for help which I told him I wouldn't do when I decided to set this computer up myself.  He does everything old school and loves Slackware which is what he ran on all of our computers until I decided to break away and attempt to do things on my own with my new computer.  In fact, I'm still running Slackware on my laptop because I don't want to change anything on that yet.

  • GumpOtakuGumpOtaku Posts: 106

    ReactOS is an interesting Opensource project which may be able to run Daz Studio when the developers get it out of Beta> that is if it does not fall to MS. It may be what we end up using to run Daz Studio in the future if MS does go subscription like Adobe. That is if DAZ does not expand its market and create a Linux branch of it great software hint hint.I bought Adobe CS 6 and I believe I will never update again. If GIMP ever gets 64bit> I will probably change over to GIMP completely. I did this with Office, I changed to LiberOffice because MS Office is too expensive and I hate greed. I think it makes people crazy and ruins good things. I like Photoshop but it was always too expensive. I'm glad Opensource >GIMP and Blender and LiberOffice are there for those of us who cannot affort to spend so much on software. I believe Opensource is here to stay but the industry is fighting it tooth and nail becuase they don't like not having complete control over everything. In American History we called these things Monopolies, and we created laws to break them up. I believe that is why Opensource is so great it keeps Monopoly in check. So this is me saying thank you to Opensource delvopers. I would also encourage everyone to donate to Opensource from time to time to keep it alive and free for everyone.

    ReactOS has a history for being notoriously bad in a live setting. In a controlled environment - a VM for example - it works out fine. But when actually installed and ran, almost everything doesn't seem to work right. I've seen a video in which one person took nearly the whole afternoon trying to get it to work. The other programs mentioned I am very satisfied with.

     

    GumpOtaku said:

    I basically followed these instructions from Cup of Linux with a couple of modifications.  The first being I went ahead and tried installing the 64 bit version because I wanted to use Iray even though the instructions say it won't work and are for the 32 bit version.  I did not install the dotnet stuff because Wine couldn't find it for whatever reason and didn't install any of those packages.  So, basically, I just installed the following packages: vcrun2005; vcrun2010; tahoma; d3dx9; and I believe I installed the corefonts, but I'm not absolutely sure about that.  I, also, made sure I was using the absolute latest version of Wine, as well as Play on Linux, and I made sure I was using the latest version of Mint 17.  I'm also running a machine with an AMD FX 8350 and a Radeon R7 460X so I'm using the FGLRX driver for my graphics.  I think one of the major differences is that my version of Play on Linux and Wine were newer than what the person who wrote the tutorial used.  The 64 bit version installed fine this time whereas the last time I tried installing with the previous version of Wine, I never did get that up and running.

    Unfortunately, in a totally unrelated issue, I managed to totally destroy my install of Linux trying to get Tomb Raider working on it and thoroughly messed up all of my graphics and lost the GUI.  I fixed that and now I can't log into Linux because I don't think it remembers my password and all of my attempts to reset the password to a new one won't work so I haven't been able to get into Linux since I managed to get DS up and running.  I'm trying to fix all that without totally reinstalling Linux.  I'm hoping to get that fixed this week.  We'll see if I'm smart enough to get that figured out.  Sigh.  I have a feeling I should have stopped while I was ahead.

    I followed the tutorial and your modifications to the tee, and still went nowhere. and I'm on a freaking GTX 750 for crying out loud!!!

    ~GO :D

    Sorry, I don't know what to tell you.  I'm not familiar enough with the different graphic cards to really know how they differ.  I can just go by what worked for me.  I'm still trying to get my feet wet with with learning how to do things on my own without running to my husband for help which I told him I wouldn't do when I decided to set this computer up myself.  He does everything old school and loves Slackware which is what he ran on all of our computers until I decided to break away and attempt to do things on my own with my new computer.  In fact, I'm still running Slackware on my laptop because I don't want to change anything on that yet.

    Thanks for at least helping. Just one last question: If your GPU is a Radeon, how the heck did you think to install DS 64bit knowing or not knowing Iray would not work?

    ~GO :D

     

  • KnittingmommyKnittingmommy Posts: 8,191
    GumpOtaku said:

    ReactOS is an interesting Opensource project which may be able to run Daz Studio when the developers get it out of Beta> that is if it does not fall to MS. It may be what we end up using to run Daz Studio in the future if MS does go subscription like Adobe. That is if DAZ does not expand its market and create a Linux branch of it great software hint hint.I bought Adobe CS 6 and I believe I will never update again. If GIMP ever gets 64bit> I will probably change over to GIMP completely. I did this with Office, I changed to LiberOffice because MS Office is too expensive and I hate greed. I think it makes people crazy and ruins good things. I like Photoshop but it was always too expensive. I'm glad Opensource >GIMP and Blender and LiberOffice are there for those of us who cannot affort to spend so much on software. I believe Opensource is here to stay but the industry is fighting it tooth and nail becuase they don't like not having complete control over everything. In American History we called these things Monopolies, and we created laws to break them up. I believe that is why Opensource is so great it keeps Monopoly in check. So this is me saying thank you to Opensource delvopers. I would also encourage everyone to donate to Opensource from time to time to keep it alive and free for everyone.

    ReactOS has a history for being notoriously bad in a live setting. In a controlled environment - a VM for example - it works out fine. But when actually installed and ran, almost everything doesn't seem to work right. I've seen a video in which one person took nearly the whole afternoon trying to get it to work. The other programs mentioned I am very satisfied with.

     

    GumpOtaku said:

    I basically followed these instructions from Cup of Linux with a couple of modifications.  The first being I went ahead and tried installing the 64 bit version because I wanted to use Iray even though the instructions say it won't work and are for the 32 bit version.  I did not install the dotnet stuff because Wine couldn't find it for whatever reason and didn't install any of those packages.  So, basically, I just installed the following packages: vcrun2005; vcrun2010; tahoma; d3dx9; and I believe I installed the corefonts, but I'm not absolutely sure about that.  I, also, made sure I was using the absolute latest version of Wine, as well as Play on Linux, and I made sure I was using the latest version of Mint 17.  I'm also running a machine with an AMD FX 8350 and a Radeon R7 460X so I'm using the FGLRX driver for my graphics.  I think one of the major differences is that my version of Play on Linux and Wine were newer than what the person who wrote the tutorial used.  The 64 bit version installed fine this time whereas the last time I tried installing with the previous version of Wine, I never did get that up and running.

    Unfortunately, in a totally unrelated issue, I managed to totally destroy my install of Linux trying to get Tomb Raider working on it and thoroughly messed up all of my graphics and lost the GUI.  I fixed that and now I can't log into Linux because I don't think it remembers my password and all of my attempts to reset the password to a new one won't work so I haven't been able to get into Linux since I managed to get DS up and running.  I'm trying to fix all that without totally reinstalling Linux.  I'm hoping to get that fixed this week.  We'll see if I'm smart enough to get that figured out.  Sigh.  I have a feeling I should have stopped while I was ahead.

    I followed the tutorial and your modifications to the tee, and still went nowhere. and I'm on a freaking GTX 750 for crying out loud!!!

    ~GO :D

    Sorry, I don't know what to tell you.  I'm not familiar enough with the different graphic cards to really know how they differ.  I can just go by what worked for me.  I'm still trying to get my feet wet with with learning how to do things on my own without running to my husband for help which I told him I wouldn't do when I decided to set this computer up myself.  He does everything old school and loves Slackware which is what he ran on all of our computers until I decided to break away and attempt to do things on my own with my new computer.  In fact, I'm still running Slackware on my laptop because I don't want to change anything on that yet.

    Thanks for at least helping. Just one last question: If your GPU is a Radeon, how the heck did you think to install DS 64bit knowing or not knowing Iray would not work?

    ~GO :D

     

    Fearless innocence? :)  I know Iray works with CPU only which is what I render in DS on my Windows drive on this same system (dual boot with each OS on their own HD).  I love Iray and if I had known it was on the horizon when I built my system, I would have definitely gotten and nVidia card.  Unfortunately, I built my new rig before Iray came out in beta in DS.  It's slow, but I like my results in Iray so much better than my results in 3Delight or Luxus, even if I can only render in CPU only mode.  I knew of at least one other person here on the thread who had gotten Iray to work in Linux so I figured, what the heck?  I wouldn't be out anything except the time if it didn't work.  I don't remember what card had, but I figured it wouldn't matter as long as Iray works in theory, I should be able to get it to work even if I can only render in CPU only mode.

  • Robert FreiseRobert Freise Posts: 4,433
    edited July 2016

    If you haven't had the experiance yet MS with Win10 changes your default programs to the MS defaults with every update I've had to go back and reset my default programs to the ones that I want

    The only reason that I haven't gone straight Linux on all my machines is because of a couple of programs that'll only run in windows

    Post edited by Robert Freise on
Sign In or Register to comment.