updated to version 8.0 and now Zephyr free not starting

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Pemar
    3Dflower
    • Feb 2025
    • 5

    #1

    updated to version 8.0 and now Zephyr free not starting

    Hello,
    I updated Zephyr free to v8.0 and now the software doesn't start. The splash screen says it 'Initializing rendering...' then I get a pop up window saying its stopped working.

    Click image for larger version

Name:	image.png
Views:	19
Size:	25.1 KB
ID:	9802
    When I press debug I get this

    Click image for larger version

Name:	image.png
Views:	17
Size:	244.4 KB
ID:	9803
    I have tried uninstalling completely and reinstalling and I still get the same.

    ​It looks as though its missing this Zephyr.pdb file, but I'm at a loss as to how to solve this?

    Thanks in advance
  • Andrea Alessi
    3Dflow Staff
    • Oct 2013
    • 1350

    #2
    Hi,

    missing pdbs are perfectly normal as those are debug information and are never shipped with any software. Only us developers have access to those. For more information on what pdb files are (and why the should not be shipped with any product) you can refer to https://learn.microsoft.com/en-us/vi...r?view=vs-2022

    Please feel free to share the log files you can find in your %appdata% directory, if present.

    Crashing like that points to Zephyr being unable to even create the main window, so either there's a third party application interfering with zephyr. Are you running a stock windows version? Which one?

    If not, make sure there's no third party software running in the background that can interfere with it.

    If you have "dell backup and recovery" installed, try uninstalling it / upgrading it to the latest version as there were some incompatibilities in the past.

    Comment

    • Pemar
      3Dflower
      • Feb 2025
      • 5

      #3
      Hi Andrea,
      Thanks for your response.
      When I initially installed it I installed it from the running Zephyr v7.X application. This subsequently closed and installed v8.0. The software wasn't able to start up as v8.0. This suggests any third party application was likely consistent between the v7 and v8, but I'll try disabling some apps and see what happens ...

      When the initial update didn't work I uninstalled completely, downloaded it again and tried reinstalling, but I got the same result.

      previous zephyr version: 3DF Zephyr Free v. 7.531

      I've attached the latest flog(txt) file from 'AppData\Local\3Dflow s.r.l\3DF Zephyr\Log' folder I've had to change the extension to txt as it prevented me from uploading a *.flog file.
      The last line of this flog file says
      "[1][10:17:43] Warning: Assert failed at \ProgressBarQt.cpp(740): Invalid progress bar finish"

      Windows version:
      Edition Windows 10 Pro for Workstations
      Version 22H2
      Installed on ‎03/‎03/‎2022
      OS build 19045.5487
      Experience Windows Feature Experience Pack 1000.19061.1000.0

      Its a HP so I'll try and see if there's the HP equivalent to the dell recovery.

      Thanks again
      Attached Files

      Comment

      • Andrea Alessi
        3Dflow Staff
        • Oct 2013
        • 1350

        #4
        Thank you for the log!

        This seems like it's getting issues starting the 3D renderer. Are you drivers up to date? If not, please update them and try again

        Comment

        • Pemar
          3Dflower
          • Feb 2025
          • 5

          #5
          Hi Andrea,

          I eventually found the issue. It was indeed a conflict with another application -> 3DxWare.

          Uninstalling '3Dconnexion 3DxWare 10' solved it.

          To confirm this I reinstalled their latest software (v10.9.3) and the issue came back.
          I know which software I'd sooner have installed!

          For additional info, whilst I was having the issue, 3DF Masquerade standalone started no trouble.

          Thanks for all your prompt responses yesterday.

          Comment

          • Andrea Alessi
            3Dflow Staff
            • Oct 2013
            • 1350

            #6
            Hi Pemar,

            thank you for the additional information! We'll look into it, I can confirm 3Dconnexion devices work with the latest version so there might be something else specific at play!

            Comment

            Working...