VectorStyler
    • Categories
    • Unread
    • Recent
    • Tags
    • Popular
    • Register
    • Login

    Does not work on Windows 10

    Scheduled Pinned Locked Moved Resolved Issues
    14 Posts 2 Posters 15.5k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • VectorStylerV Offline
      VectorStyler @Ingolf
      last edited by

      @Ingolf Check if there is a c:\Users<User Name>\NumericPath\ folder. That is where VS stores its local user settings (if it manages to launch).
      Then in C:\Documents and Settings\All Users\Application Data\NumericPath\ if there are crashes.

      IngolfI 1 Reply Last reply Reply Quote 0
      • VectorStylerV Offline
        VectorStyler @Ingolf
        last edited by

        @Ingolf Do you have OpenCL driver installed on your system?

        IngolfI 1 Reply Last reply Reply Quote 0
        • IngolfI Offline
          Ingolf @VectorStyler
          last edited by

          @vectoradmin No, GPU chipset too old. Where is it installed? I tried once, I think.

          🍏 macOS Sequoia Apple Silicon

          VectorStylerV 1 Reply Last reply Reply Quote 1
          • IngolfI Offline
            Ingolf @VectorStyler
            last edited by

            @vectoradmin Log example:

            crash log from windows version: crashed
            user: Kode
            crashed thread: 2872

            thread count: 1

            begin: Crashed thread: 2872, FFFFFFFFFFFFFFFE
            0: ?? - PC: 0x7ffc631f1ef6 Stack: 0xc07437dca0 Frame: 0xc07437e410
            1: ?? - PC: 0x7ffc631f1d9e Stack: 0xc07437e420 Frame: 0xc07437e4b0
            2: ?? - PC: 0x7ffc631f1c47 Stack: 0xc07437e4c0 Frame: 0xc07437e4e0
            3: UnhandledExceptionFilter - PC: 0x7ffc69dbc247 Stack: 0xc07437e4f0 Frame: 0xc07437e600
            4: memset - PC: 0x7ffc6c074b63 Stack: 0xc07437e610 Frame: 0xc07437e640
            5: _C_specific_handler - PC: 0x7ffc6c05bb16 Stack: 0xc07437e650 Frame: 0xc07437e6b0
            6: _chkstk - PC: 0x7ffc6c07130f Stack: 0xc07437e6c0 Frame: 0xc07437e6e0
            7: RtlRaiseException - PC: 0x7ffc6c01b5e4 Stack: 0xc07437e6f0 Frame: 0xc07437edf0
            8: KiUserExceptionDispatcher - PC: 0x7ffc6c06fe3e Stack: 0xc07437ee00 Frame: 0xc07437f4f0
            9: ZValueFileCollection::setupMenuState - PC: 0x7ffc1e14b3ef Stack: 0xc07437f500 Frame: 0xc07437f530
            10: ZValueFileCollection::setupMenuState - PC: 0x7ffc1e14c99d Stack: 0xc07437f540 Frame: 0xc07437f5f0
            11: ZValueFileCollection::setupMenuState - PC: 0x7ffc1e14cc49 Stack: 0xc07437f600 Frame: 0xc07437f700
            12: ZHostWindow::resetIcon - PC: 0x7ffc1e164db3 Stack: 0xc07437f710 Frame: 0xc07437f730
            13: ZHostWindow::open - PC: 0x7ffc1e1649a3 Stack: 0xc07437f740 Frame: 0xc07437f760
            14: ZWindow::openHost - PC: 0x7ffc1e021c29 Stack: 0xc07437f770 Frame: 0xc07437f790
            15: ZWindow::open - PC: 0x7ffc1e021a4a Stack: 0xc07437f7a0 Frame: 0xc07437f7f0
            16: ZView::openWindow - PC: 0x7ffc1e04f0fe Stack: 0xc07437f800 Frame: 0xc07437f950
            17: ZView::open - PC: 0x7ffc1e04e5b5 Stack: 0xc07437f960 Frame: 0xc07437f980
            18: ZApplication::loadMainView - PC: 0x7ffc1e0a7faf Stack: 0xc07437f990 Frame: 0xc07437f9b0
            19: ZApplication::loadMainVisual - PC: 0x7ffc1e0a8020 Stack: 0xc07437f9c0 Frame: 0xc07437f9e0
            20: ZApplication::launchCompleted - PC: 0x7ffc1e0a69c0 Stack: 0xc07437f9f0 Frame: 0xc07437faa0
            21: ZHostUI::mainLoop - PC: 0x7ffc1e15808d Stack: 0xc07437fab0 Frame: 0xc07437fad0
            22: ZApplication::run - PC: 0x7ffc1e0ac90b Stack: 0xc07437fae0 Frame: 0xc07437fb00
            23: zcfMain - PC: 0x7ffc1e150a69 Stack: 0xc07437fb10 Frame: 0xc07437fba0
            24: ?? - PC: 0x7ff6c5c01086 Stack: 0xc07437fbb0 Frame: 0xc07437fbe0
            25: ?? - PC: 0x7ff6c5c015de Stack: 0xc07437fbf0 Frame: 0xc07437fc20
            26: BaseThreadInitThunk - PC: 0x7ffc6b4d7034 Stack: 0xc07437fc30 Frame: 0xc07437fc50
            27: RtlUserThreadStart - PC: 0x7ffc6c01d0d1 Stack: 0xc07437fc60 Frame: 0xc07437fcd0
            28: RtlUserThreadStart - PC: 0x7ffc6c01d0d1 Stack: 0xc07437fc60 Frame: 0xc07437fcd0
            end: Crashed thread: 2872

            🍏 macOS Sequoia Apple Silicon

            1 Reply Last reply Reply Quote 0
            • VectorStylerV Offline
              VectorStyler @Ingolf
              last edited by

              @Ingolf The missing OpenCL is the problem!

              First: I have to fix this, as this should not be required 🙂

              Second: You could try to install OpenCL, as described in:
              https://software.intel.com/content/www/us/en/develop/articles/opencl-drivers.html and
              https://streamhpc.com/blog/2015-03-16/how-to-install-opencl-on-windows/

              Thanks for letting me know, this is a serious issue in VS.

              IngolfI 1 Reply Last reply Reply Quote 1
              • IngolfI Offline
                Ingolf @VectorStyler
                last edited by

                @vectoradmin Installing opencl helped a bit, now the app starts. First dialog is a crash dialog but the program still works. I filled the dialog out and send the report.

                No crash logs this time.

                🍏 macOS Sequoia Apple Silicon

                IngolfI 1 Reply Last reply Reply Quote 0
                • IngolfI Offline
                  Ingolf
                  last edited by

                  For your to do list: It looks like VS doesn't use the monitor profile I have configured in Windows. I have a wide gamut screen so the colors will look awful. 🙂

                  🍏 macOS Sequoia Apple Silicon

                  VectorStylerV 1 Reply Last reply Reply Quote 1
                  • VectorStylerV Offline
                    VectorStyler @Ingolf
                    last edited by

                    @Ingolf Added this to the backlog.

                    1 Reply Last reply Reply Quote 1
                    • IngolfI Offline
                      Ingolf @Ingolf
                      last edited by

                      @Ingolf Crash report only happened on the first launch. Not seeing it anymore.

                      🍏 macOS Sequoia Apple Silicon

                      VectorStylerV 1 Reply Last reply Reply Quote 1
                      • VectorStylerV Offline
                        VectorStyler @Ingolf
                        last edited by

                        @Ingolf Thanks for letting me know.
                        I will fix the OpenCL issue, and will look into the monitor profile problem also.
                        Meanwhile, the Display color settings of VS can be set in the Styles -> Color Settings menu, if that helps.

                        IngolfI 1 Reply Last reply Reply Quote 0
                        • IngolfI Offline
                          Ingolf @VectorStyler
                          last edited by

                          @vectoradmin said in Does not work on Windows 10:

                          @Ingolf Thanks for letting me know.
                          I will fix the OpenCL issue, and will look into the monitor profile problem also.
                          Meanwhile, the Display color settings of VS can be set in the Styles -> Color Settings menu, if that helps.

                          Thank you for ultra-fast and competent help! 🤝

                          Vectorstyler looks extremely interesting - and bizarrely feature rich already! You should really stabilize, mature and polish VS now. I can only say WHOW.

                          Prepare for a bombardement of suggestions, bug reports and usability suggestions. 😅

                          🍏 macOS Sequoia Apple Silicon

                          1 Reply Last reply Reply Quote 1
                          • First post
                            Last post