Building on Linux

[brentnd]

When building and running, this is what I see:

The sky moves around with mouse movement but the window cannot be expanded.

Commands:

sudo make install
make linux
./RepGame

Environment:

• Branch: master
• Ubuntu 18.04
• gcc 7.3.0
• freeglut 2.8.1-3
• glew 2.0.0-5
• glm 0.9.9~a2-2
• nvidia-cuda-toolkit 9.1.85-3ubuntu1
• rsync 3.1.2-2.1ubuntu1

Any ideas?

[Repkap11]

If you type "i" it should open your inventory, free your mouse, and let you maximize the window. I'm not sure why you can't see the world...

…

On Mon, Apr 1, 2019, 2:15 PM Brent Dimmig ***@***.***> wrote: When building and running, this is what I see: [image: image] <https://user-images.githubusercontent.com/4182027/55349471-cf7e7480-5487-11e9-9b22-fb320085d77d.png> The sky moves around with mouse movement but the window cannot be expanded. *Commands:* sudo make install make linux ./RepGame *Environment:* - Branch: master - Ubuntu 18.04 - gcc 7.3.0 - freeglut 2.8.1-3 - glew 2.0.0-5 - glm 0.9.9~a2-2 - nvidia-cuda-toolkit 9.1.85-3ubuntu1 - rsync 3.1.2-2.1ubuntu1 Any ideas? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#7>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFSKpxknLnvOmxeaEycpZs6VCJ_5bp_6ks5vckzPgaJpZM4cWVcG> .

[brentnd]

Cool, "i" helped me get to what looks like a broken inventory and maximize the window.

No notable logs or errors in the console output during that. Seems like I'm maybe missing resources or sprites.

[brentnd]

Could it be something with this?

https://github.com/Repkap11/RepGame/blob/master/src/common/abstract/textures.cpp#L65

Do I need to symlink the bitmaps to /system/bin or something?

[brentnd]

Nevermind, I guess that's just for caching the textures.

[Repkap11]

That path is for Android, which has strange paths. The image should be this one.
https://github.com/Repkap11/RepGame/blob/master/bitmaps/textures.bmp
Its looked for relative to the executable as bitmaps/textures.bmp

[brentnd]

Yeah, I did some debugging and texture_init_blocks and texture_init_sky are both resolving the correct path for the bitmaps.

[Repkap11]

Could be your GPU doesn't support the texture mode I'm using. Do you get black ground if you comment out the "discard" in chunk_fragment.glsl?

[brentnd]

I commented out each "discard" individually and all of them together and didn't see any difference in the ground color.

[Repkap11]

Ahh, comment out the #include cuda.mk inside linux.mk
I didn't realize the install instructions will let you install the nvcc compiler even if the host doesn't support cuda acceleration.

[brentnd]

Okay, with cuda commented out and rebuilt, it starts like it did before then the screen goes back around 5 seconds. Inventory is still a bunch of black boxes.

Something I just thought of is that I am running this on a vagrant VM with virtualbox. Could that be problematic?

[Repkap11]

Try "make map" to delete your "World1" directory.
I still can't explain the blackness.
It looks like your VM has OpenGL 3.3 core, which is what it needs.

[brentnd]

Okay, seems a bit better now. I can move around and see black blocks where the world has actually generated ground (instead of just the while abyss from before). Still no textures on inventory either so seems like that's what remains. Could be lack of graphic resources on my VM.