How to fix object selection in a viewport?

I have did something with the viewport setup (I guess) and now when I’m selecting any actor (including a SkySphere – it’s the most terrible) the actor becomes fully “outlined” in all projects – see the screenshot.

113173-selected.png

How can I disable such thing and make it by default only a “stroke” on selection? I’ve tried to reset to default setting – but it didn’t helped. I’ve found that this “outline” could be turned off in Preferences → Level Editor → Viewports → Use Selection Outline, but then the selected actor will not be highlighted at all…
How to restore the default preferences?

Hi norlin,

It looks like your selection highlight intensity. If you don’t want the orange fill color on selected objects make sure that you have a value of 0.

let me know if that helps,

Ed

For me this parameter does not make any visible effect (tried 0, 0.3, 1 – all looks exactly the same), as on screenshot:

I see, in that case I’m unable to reproduce your issue.

If this is only happening in this project try deleting your saved and intermediate folders in your project directory (don’t worry this wont hurt anything). I would also delete your config folder as this is what holds your project settings (make a copy of this just in case if you don’t want to lose your input settings/preferences).

If this is happening in all your projects, could you try verifying your engine

112852-verify.jpg

and if that doesn’t catch anything try a clean reinstall of the engine. There may be a chance that your default preferences got corrupted if this is happening in all projects.

It happens for all my projects and begins after I’ve played a bit with a SkySphere once… (not sure how it’s related).

About reinstall – I thought that method is only to fixing Windows issues :smiley:
Beside jokes – is it enough just to remove the engine version from Epic Launcher and then install it again? Or need to clean anything manually? I’m on macOS.

Well, it didn’t helped… The selection looks the same.

No you shouldn’t have to do anything manually. Removing the engine via the launcher then reinstalling is fine.

Nope, didn’t helped…

In case if it could help, I can control the color of such selection with “General → Appearance → Selection Color”. But it still painting whole object instead of just border outline…

Alright, this may be a compatibility issue. Could you provide your system specs for your mac so I may test on a mac machine on our end. The tests I ran earlier were on a windows machine and may not catch the issue.

When I have installed UE4 at the first time (few weeks ago, 4.12) It was ok for the same mac… And the issue definitely appeared after my update to 4.13 (just I’m not 100% sure if it was right after update, or after some time).
Will try to install 4.12 to check it now.

My specs:

113302-specs.png

Ok, now I can confirm: it does not happens in UE4.12.5, but happens in 4.13.2 and 4.14.0 Preview 2.

Could you include your video card information. Click on “about this mac” then in the window at the bottom you will see a button “system report…” a window will pop up labeled MacBookPro. Find the Graphics/Displays tab in the list on the left. Take a screenshot of your video cards. (see screenshot example)

Sure, here is it:

113325-graphics.png

If your only graphics card is the Intel Iris 6100 then that is a problem. That card isn’t recommended for running the engine. Look for a NVIDIA GeForce GT card (probably 750M).

If you do have this card, make sure that your mac is switching to use this card when launching the engine.

I have only this card (it’s a macbook, so I can’t change it), and as I said it’s working good with UE 4.12.
And I don’t see any other issues, except this outline.

Hi Norlin,

Unfortunately, we don’t have your specific setup to test with. If you are still able to reproduce the issue with updated hardware you can reopen this post. Otherwise, I can’t reproduce the issue and must mark this post as resolved for tracking purposes.

Thank you for your patience,

Ed

Whoa, that was not expected… What for you need the same setup? I can provide logs or whatever needed… Or even can give you a remote accss for debugging…
Again, this bug was inserted only in 4.13, so it’s definitely not about my hardware issue.