Object mask about unrealcv

[Noelok]

Hello,
Am I the only one with this issue?

[qiuwch]

Hi, @Noelok "IndentationError: unexpected indent" sounds like a python error. Where did you see this error? Can you paste more detailed error message?

For the can not connect to error, there might be several reasons. The most common issue is port 9000 is in use. Can you run vget /unrealcv/status and see what it returns?

[Noelok]

Hi Weichao,
Thank you for your reply.
Here is a screenshot of the error msg I've got when I tried to connect to my unreal scene with unreal launched from a command shell.

The UnrealCV plugin is installed :

Because I couldn't connect, I exported my scene as a package for windows 64bits. I launched the package and I was able to connect using a command shell. When I run the command "vget /unrealcv/status" I got this: "Is listening\nClient Connected\9000\n"

The "IndentationError: unexpected indent" message is when I run this command from a command shell:
"vset /object/[object_name]/color 255 0 0" . I'd like to set an ID color to my object

Thank you for your help,
Noel.

[qiuwch]

For the first question: when you are not able to connect to the editor using python script, you can still type command in the console of UE4 Editor. It will be something looks like this, I want to see the status in the editor.

[lostoliv]

Hi @qiuwch, thanks for this plugin.

I have a very similar issue. I compiled everything from source for UE 4.13.
I created a package from the Realistic Rendering UE4 scene in the marketplace.

When starting the standalone scene, then trying to connect the client from python, it's failing to connected (see screenshot below).

Note that the same thing is working if I use the version of Realistic Rendering downloaded from your website or if I build the package in UE 4.12 with your plugin.

But using the version compiled from latest github with UE 4.13, no luck...

Thanks!
-olivier

[qiuwch]

Hi @oliviersoares:

I did not do a lot of testing with 4.13 yet. This is weird, let me do some diagnosis and get back to you tomorrow.

[lostoliv]

Thanks @qiuwch, much appreciated.

I did a test with 4.12, compiled from the same source (latest github) and I could make everything work nicely. So it seems to be an issue with 4.13.

Note that I still have the same issue Noel described which is when playing the scene directly from Unreal, the client won't connect. However it will connect properly when building a standalone package.

As a side note, for 4.13 to work, I had to change this line from an Error to a Warning:
https://github.com/unrealcv/unrealcv/blob/master/Source/UnrealCV/Private/TcpServer.cpp#L267

Without this change, Unreal generates an error when building the package and fails (might be related to the underlying issue with 4.13).

Thanks again,
-olivier

[Noelok]

Hi Weichao,
Sorry for my late reply.
So in 4.12, when I run the command "vget /unrealcv/status"
I got this :

I have to open the Output Log to see the result of this command.
thanks,
Noel.

[qiuwch]

Hi, @Noelok @oliviersoares:

Sorry for getting back to you after such a long delay.
The compatible issue should be fixed in the v0.3.0, if you are still interested in using this tool, please give it a try. Thanks.

[Noelok]

Hi Weichao,
Thanks for the update! We are really interested in using this tool! :)
I'm testing it in 4.13
Thanks!

[qiuwch]

Thanks for feedback and let me know if you find any issue. : )