-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not find an open Unreal Editor Instance #3
Comments
My iMac also shows "Could not find an open Unreal Editor Instance" when I use Blender 3D (send2UE). |
Sorry I missed your comment. I haven’t tried on osx, so I can’t tell if their code is working
We are both using the same code provided by epic to do the handoff between blender/spp and ue. So if it is not working in blender I doubt it would work with my plugin. just to get a bit more insight from you guys :
|
Hi Ffancoisgfx, I found Blender cannot location the UE5 received folder, |
I cannot tell about the Blender plugin, I am not the developer. Which folder are you talking about ? If Enable Remote Execution where not enabled before, it would have not worked. Could you share a screenshot of your settings ? Or perhaps share the error if you have a message.ThxLe 21 janv. 2024 à 11:19, cylamhk ***@***.***> a écrit :
Hi Ffancoisgfx,
The Blender & UE are running in the same iMac. AND
also follow your suggestion to enable the “Enable Remote Execution”.
It cannot communication each other.
I found Blender cannot location the UE5 received folder,
can I change the "send" and "receive" folder, so that they can make a channel of its pipline?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Also having this problem. Any solutions? |
hey, it detects UE 5.4.2 on win 11 23H2 + Substance Painter 10.0.1 |
[Python] "Could not find an open Unreal Editor Instance" and "No Unreal Found" in the dropdown inside SEND TO UNREAL. Tried restarting both UE and SP.
Substance Painter 8.3.1. UE 5.2 macOS 14.3.
The text was updated successfully, but these errors were encountered: