Not getting any 3D effect

I’m just adding cubes to the Sample Scene… I assume I’ve missed a step. The cubes are not 3D on the phone’s display. Just 2D, but with that lenticular lens effect that tells me that it’s in 3D mode.

Here’s an image of my Unity setup with the camera selected.

@tuck Are you using Unity Remote or are you packaging the app and installing the .apk on the device?

If you’re using Unity Remote, you also have to use the LeiaRemote app from the Leia Developer portal to ensure the backlight is turned on, otherwise the interlacing will show with the standard 2D backlight instead of the Leia Diffractive Lightfield Backlight.

Thanks Nima.
Interesting. I am using the LeiaRemote app, which required the installation of Unity Remote 5.
I could perhaps package up the scene and run the .apk I guess. Would that ensure better performance of the 3D effect?

When I built it to device, the 3D effect didn’t turn on. It was in 2D mode.

The 3D effect really works well when built to device. It seems that it’s only the LeiaRemote app that is not displaying as advertised.
But at least I can get it to work now.

I think the script for 3d in a build APK is different from the LeiaRemote script for building the app inside Unity.

That would explain what I’m seeing. The 3D effect is still not working when using LeiaRemote for me.

Do you see an image on the device when using the remote tool or can you see the image and just the 3D is not working? This will help me know if it is a Unity Remote issue or a bug in the SDK.

Try using using this version of the LeiaRemote.cs script.

Also In the Project Settings -> Unity Remote settings change Compression to PNG instead of JPG. If the image uses JPG compression the image will not be pixel perfect which is necessary for the image to be viewed on the device correctly.

The image (3 cubes) appears on the device. However they’re not 3D. They’re your standard 2D image.
When I build the .apk and run that, the cubes are all fully “holo” 3D. It’s super cool when it works.

1 Like

Finally got it to work.
There is a setting in Project Settings/Editor called Unity Remote/Resolution. My setting seems to have been set on “Downsize” and this seems to have been preventing LeiaRemote from showing the true “3D” effect in remote mode when playing in Editor.
Changing this setting to “Normal” seems to have fixed it.
Thanks for all your help everyone.


Hi there!
Fooling around with mij Lumepad and Unity for a few days now, having a lot of fun. But it seems I don’t get LeiaRemote working properly…
I do get the 2D version on the Lumepad, by opening Unity remote myself. Because nothing happens when I run only LeiaRemote and push the play button of the Leialogo project in Unity. As I understand the LeiaRemote app should put the LumePad in 3D mode… but as I said: the LeiaRemote doesn’t open Unity remote automatically. When I open LeiaRemote myself and click the Unity Remote button it states it can’t find Unity Remote and I should intall it. But I have…
Any Ideas?

Oh, wait, solved it! :grinning:
Forgot to ad the LeiaRemote script to the scene :grimacing:


Glad you got that to work! For anyone who faces a similar issue, be sure to attach the Leia Remote script to any game object in the scene, along with the steps listed here:


Did you have to do anything special to get your lume pad to show up in unity? My red shows up as a device and I have that device working, but can’t seem to get my lume to display…

Hi Landon, no i didn’t do anything other than stated in the discription above.
You could check the connection by typing “adb devices” in the terminal. It should give an answer witch devices are connected.
Hope this helps.
Oh, if it states it can’t find the adb command, you should install the android sdk.

1 Like

Adding onto what Thomas said, you can find details on adb on the Android developer page here

1 Like

When you connect your Lumepad by USBC to your dev machine, does a “Use usb for …” window pop up on your Lumepad?

If not, confirm the Lumepad is in “developer” mode. Lumepad > Settings > About > Build number > push “Build number” x 7.