Page 2 of 2 FirstFirst 12
Results 16 to 23 of 23

Thread: Layout UI in LW10.1 gets weird colors

  1. #16
    Member
    Join Date
    Sep 2006
    Location
    Goteborg, Sweden
    Posts
    207
    Quote Originally Posted by Danner View Post
    The problem happens when you load a 10.1 (or newer) scene in 10.0 or older Lightwave.
    The config gets confused with the new naming conventions of the color space and it gets screwed up. Recreate your
    configs by deleting them and restarting lightwave. Make a backup of the configs while you are at it. Or better yet,
    use a newer version of Lightwave.
    Yes, that is one part of the problem. But I have only one version on my laptop. Not two different. If I donīt put the
    Layout configs in the trash-bin before I start I get weird UI-colors. So itīs not just a mix between 10.0 and 10.1 issue
    as I don't have more than one install on this computer.

    Backup of corrupted configs dosenīt seem to be very smart.

    A newer version is always a safe answer to everything, but this is about very a basic function in the software.
    It is about the UI. How people are able to use the interface. It is fundamental.

  2. #17
    It's not because you have two versions, it's because you loaded a newer scene that is in that respect incompatible with the older versions of lightwave. This did happen to me once, fixed it, then installed the next point realease shortly afterwards. Back then there was a message posted by someone at newtek with instructions on how to handle this issue and why it happened, it was a mess, and apparently still is for people needing to use older versions for watever reason. When Lightwave gets fixed it does it with newer versions, instead of patches so unless you upgrade you have to deal with this.

    You can fix your config to a working one by editing it. Just Remove the quotes around the colorspace presets.

    So where it reads:
    EndPlugin
    ColorSpaceViewer "sRGB" "none"
    ColorSpaceSurfaceColor "sRGB" "none"
    ColorSpaceLightColor "sRGB" "none"
    ColorSpacePaletteFiles "sRGB" "none"
    ColorSpace8BitFiles "sRGB" "none"
    ColorSpaceFloatFiles "Linear" "none"
    ColorSpaceAlpha "Linear" "none"
    ColorSpaceOutput "sRGB" "none"
    ColorSpaceOutputAlpha "Linear" "none"

    change it to:
    EndPlugin
    ColorSpaceViewer sRGB none
    ColorSpaceSurfaceColor sRGB none
    ColorSpaceLightColor sRGB none
    ColorSpacePaletteFiles sRGB none
    ColorSpace8BitFiles sRGB none
    ColorSpaceFloatFiles Linear none
    ColorSpaceAlpha Linear none
    ColorSpaceOutput sRGB none
    ColorSpaceOutputAlpha Linear none
    Last edited by Danner; 02-06-2013 at 04:50 AM.

  3. #18
    Member
    Join Date
    Sep 2006
    Location
    Goteborg, Sweden
    Posts
    207
    Quote Originally Posted by Danner View Post
    change it to:
    EndPlugin
    ColorSpaceViewer sRGB none
    ColorSpaceSurfaceColor sRGB none
    ColorSpaceLightColor sRGB none
    ColorSpacePaletteFiles sRGB none
    ColorSpace8BitFiles sRGB none
    ColorSpaceFloatFiles Linear none
    ColorSpaceAlpha Linear none
    ColorSpaceOutput sRGB none
    ColorSpaceOutputAlpha Linear none
    Thank you for your suggestion.

    I did change the lines in the config file exactly as written here.
    Then I opened Layout and got this on my screen:

    Click image for larger version. 

Name:	Screenshot - 2013-02-06-error.png 
Views:	88 
Size:	193.6 KB 
ID:	111193

    It is easier to trash the configs before opening Layout. Then it works.
    And I know I can solve it if I update for 695 USD.

  4. #19
    Odd that the change didn't work. Is that the latest version of LW you can download if you log in to your NewTek user account?

  5. #20
    Member
    Join Date
    Sep 2006
    Location
    Goteborg, Sweden
    Posts
    207
    Quote Originally Posted by Danner View Post
    Odd that the change didn't work. Is that the latest version of LW you can download if you log in to your NewTek user account?
    I thought the same and decided to update. So I did that and also added the -c thing to the shortcut in order to separate configs. It is running now. But I have no clue on how long it will work. Lets see.

  6. #21
    automator of tasks xchrisx's Avatar
    Join Date
    Jul 2003
    Location
    Nevada
    Posts
    593
    Blog Entries
    6
    Or once you get your 10.0 configs setup properly... make them readonly and it should prevent it from getting screwed up. But realistically you should use 10.1 and ditch your old install of 10.0
    My Lscript Collection | LinkedIn
    3D Generalist IGT

  7. #22
    Member
    Join Date
    Sep 2006
    Location
    Goteborg, Sweden
    Posts
    207
    HI,
    I made a new install and after that it has worked as expected. So, it is obvious the former
    was 10.0 but now I have 10.1
    I have opened different scene-files from different sources and I have closed Layout a few
    times and started again. Before I did not quit Layout during the day because of the problems.

    And Danner, thank you for your patience and all suggestions in order to find a solution.
    It helped at last. I appreciate your support.

    Now it is easier to focus on the tasks at hand.

  8. #23
    Glad you got it sorted.

Page 2 of 2 FirstFirst 12

Tags for this Thread

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
  •