Weird artifacts on screen when running first-person no-content with simple debug message

Development Programming & Scripting C++
1

Hi,

I’m wondering if someone has an idea or knows why I might be seeing this on screen when running my simple cooked Linux content (UE 4.8).

Nvidia GTX980, I7, 24 GB ram. Looks like there is a ton of blur on screen as I move the camera.
I can fire the gun fine (basic ball projectiles), and I see my debug message in yellow, as expected.

(NOTE: it is the only custom code present – inside the Character.cpp – see below).

This is a simple test, no real code yet, just wanted to run the cooked content in linux.

I’ve tried “With starter content” and “No starter content” ; same thing.

Code added to MyCharacter.cpp (by using UE4 editor – add c++ code to class) is:

(on top):
#include Engine.h

(in fire function):

static const FString ScrollingMessage(TEXT("Debug message: "));  

if (GEngine)  
{  
    const int32 AlwaysAddKey = -1; // Passing -1 means that we will not try and overwrite an   
                                  // existing message, just add a new one  
    GEngine->AddOnScreenDebugMessage(AlwaysAddKey, 0.5f, FColor::Yellow, ScrollingMessage);  
}

and nothing else.

Screenshot:
http://picpaste.com/pics/FP_NC_001__64-bit__GLSL_150__003-FTdRw91Q.1435103077.png

Thanks

2

Definitely looks like a bug to me. I’d post it on AnswerHub so EPIC can check it out. It would be interesting to know if it ran ok with 4.7.

For the string you print, I’d try just manually putting in FString(“Hello World”) or something. I’ve had occasions where using static const variables gives weird pointers depending on your compile settings. Probably just my own incompetence though :slight_smile:

3

[solved]

Thank for your quick reply. I fixed it.

I just had to specify -opengl4 on the command line (as an argument) when running the game. All the artifacts are gone.