After installing the newest version Nomad won’t start at all.
And I just post a “Download version” thread. DAMN IT!
Now what?
After installing the newest version Nomad won’t start at all.
And I just post a “Download version” thread. DAMN IT!
Now what?
I don’t even know which version you are talking about? Windows? Macos? Ipados?
There is so much time wasted with these useless back & forth messages…
What does it mean doesn’t start exactly? Crash? Blank screen? Nothing?
“There is so much time wasted” …
Ok I will short from now on.
Windows.
White screen for 2 seconds and then close.
In your Nomad folder (usually one of these paths unless you changed it):
C:\Users\<username>\AppData\Local\Nomad Sculpt\data\
C:\Users\<username>\Documents\Nomad Sculpt\
C:\ProgramData\Nomad Sculpt\
Do you have a crash.log file in one of these folder?
Also can you try renaming (do NOT delete) settings.json to anything else and then restart Nomad?
\AppData\Local\Nomad Sculpt\data
Folder not exist in my PC:
C:\Users\\Documents\Nomad Sculpt\
\ProgramData\Nomad Sculpt
Only license.
Changing the settings to COMBO_settings,json will not help
I will maybe need to restart my PC.
Is nomad_folder.txt empty?
Also check in
C:\ProgramData\Nomad Sculpt\
Rename config.json and try to restart Nomad (it worked for someone else, but I don’t know if it’s the same issue).
As written!
C:\ProgramData\Nomad Sculpt\
Only license there.
Is fine! I will figure it out!
Do not want to waste your time!
Thanks anyway!
Oops wrong path, sorry I meant:
C:\Users\<username>\AppData\Local\Nomad Sculpt\config.json
You can rename this file and restart Nomad. (do NOT delete these config files).
Please do not “figure it out”… this is simply the worst scenario for me because people simply delete files and then I can’t fix the issue and I’m in the complete dark after that (I cannot replicate any of these crashes)
Now Nomad is back.
With a couple of issues as you can see. But my model and the interface ist there.
Looks like it is working.
I will need to test.
I just read this now. QUOTE [Please do not “figure it out”…]
I solved the problem.
This message is normal.
I solved the problem.
Did renaming config.json helped?
Here on of the solution. If you want to hear/know how I solved the issue.
I am not aware about your Windows coding knowledge.
But I needed to clean the temp files because the error was kind of storage there.
Since the program was called and then close immediately again, windows sometimes - NOT always, writes some errors that will be call always there! And then is a problem because windows will call an error and not an run program.
None of the .json help me!
Try uninstalling and reinstalling it; I ran into a bug once and used that method, and everything was fine afterwards.