You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to debug the scene, as objects will be randomly positioned, as well as lights, and cameras around the POI, in an iterative manner.
I see you have thought about running Blender GUI with blenderproc degub, but that does not give me the possibility to do breakpoints.
When I run the script with the debugpy and the port you indicate (5678), I can instead use breakpoints and debug my data generation along the way, if needed.
Example script:
But to me the ideal debugging experience in VSCode would be running the Blender 3.5 instance as the Blender Development extension does, and then, with the target script open, attach to the stack of such extension. I don't know if this is possible, but it would be great!
Unfortunately, I think this extension cannot source the same python environment where blenderproc is installed...
I am also trying to attach to the same debugpy run by the extension, but I get the error that the port is already busy
I will be doing some testing on my linux machine tomorrow, unless you tell me it a lost cause
Minimal code example
No response
Files required to run the code
No response
Expected behavior
Debugging is working as expected, just a suggestion/improvement
BlenderProc version
2.7.0
The text was updated successfully, but these errors were encountered:
Describe the issue
Hi, thanks in advance for ur time and help!
I am trying to debug the scene, as objects will be randomly positioned, as well as lights, and cameras around the POI, in an iterative manner.
I see you have thought about running Blender GUI with
blenderproc degub
, but that does not give me the possibility to do breakpoints.When I
run
the script with thedebugpy
and theport
you indicate (5678
), I can instead use breakpoints and debug my data generation along the way, if needed.Example script:
But to me the ideal debugging experience in VSCode would be running the Blender 3.5 instance as the
Blender Development
extension does, and then, with the target script open, attach to the stack of such extension. I don't know if this is possible, but it would be great!Unfortunately, I think this extension cannot source the same python environment where blenderproc is installed...
I am also trying to attach to the same
debugpy
run by the extension, but I get the error that the port is already busyI will be doing some testing on my linux machine tomorrow, unless you tell me it a lost cause
Minimal code example
No response
Files required to run the code
No response
Expected behavior
Debugging is working as expected, just a suggestion/improvement
BlenderProc version
2.7.0
The text was updated successfully, but these errors were encountered: