So I started with a stock fps project to test the performance on my android device (Samsung Galaxy s3 GT-I9300 Mali400 GPU android 4.3 Jelly bean) the preview in the editor itself was fine but when I launched it on the physical device the geometry was invisible!
Although the technically the geometry is still present as you can tell by observing the physics
you can see that the projectiles are bouncing off the invisible wall! also the floor on which the character is standing is a geometry but because its not being rendered you can see the height fog below
Of course converting them to static mesh will work as other static meshes like the boxes in game work fine! but I want the game to render the BSP as well.I cannot manipulate static mesh like the BSP so I need BSP brushes to render! I know the engine is still under heavy development but still for some reason the quality looks crappy on the device while the epic citadel demo was just awesome
I had a colleague of mine test your issue on your device and we are getting the same results. This should not be occurring and I have made the developers aware of the issue. We tested it on other devices as well to see if it was in fact S3 specific, and this seems to be the case. Whether we packaged it out as “All,” or for “ETC1” we got the same result.
We appreciate your report and will be working to have this issue resolved when we can. In the meantime, one suggestion I have as a workaround would be to go ahead and convert any of the BSP’s to static meshes when you have the textures and shapes how you would like them to appear in game.
I just returned from my break/vacation over the Holidays. Apologies for the late response, but I just looked into the issue that originally reported and it is on the map to be fixed.
They found the reason for this error is as follows:
"UModel uses FRawIndexBuffer16or32, which is actually a 32-bit index buffer.
There is code in RawIndexBuffer.h that looks like this: #if DISALLOW_32BIT_INDICES
// if 32 bit indices are disallowed, then use 16 bits in the FRawIndexBuffer16or32
But unfortunately nothing actually defines DISALLOW_32BIT_INDICES in UE4, and in any case we probably want to make this decision at runtime based on hardware capabilities."
Since we know the location and source of the error, we can now have it assessed based on the current workload and relevance of this issue compared to others within the engine.
This is currently all the information I can provide to you at this time, but rest assured it is on the agenda to be fixed. We appreciate your patience as always and let us know if you have any other questions.
We are modifying our preview process to release earlier in the development cycle so our developer-community can help us catch issues sooner, and we will release updated previews during the development cycle.
Please be aware that the preview releases are not fully quality tested, that they are still under heavy active development, and that they should be considered as unstable until the final release. Developers should not convert their projects for active development on preview releases. Please test on copies of your project instead.