2.39
...
·
·
1
like
|
|---|
Sorry for the vague header. If I put the word Graxpert in it, AI will move the post. I have two near identical Windows 11 desktops running PI. Graxpert runs on one, but not the other. It used to work on both. On the nonfunctioning pc, PI actually calls up Graxpert but then just quits without any message as to what happened and doesn't treat the image. I copied the js and xsgn files from the script/toolbox folder on the working pc and replaced the files on the nonworking pc. Didn't fix the problem. Any ideas?
|
9.89
...
·
|
|---|
You gotta give us a bit more, like what version of PI is running on both and what version of Graxpert as well what Graxpert installation are you using (or try to) on both. Oh, whether you use a modified tensorflow.dll (for GPU usage) or not.
|
|
2.39
...
·
|
|---|
OK! You're so dang good, you found the problem without even trying. It's not installed on the nonworking pc. I guess I thought it was working at one time. Maybe the gradients were so that I didn't notice that it didn't fix them. I'm shooting in a full moon and the gradients were drastic, hence the notice. That's the best I can come up with. It's that, or admit to stupidity, and I ain't doin' that.  |
0.00
...
·
|
|---|
There's no error message in the process console? The easiest thing to try might be to check "Custom app.path" in the process window and then navigate to the GraXpert app so that you're sure it knows where it is. There's also an option there to add extra GraXpert logging information into the process console which might help.
|
0.00
...
·
|
|---|
Seriously update your pix insight and just use gradients correction. Two clicks. That grax pert was a pain in da ass
|
