Atomic Systems

I recently got a replacement monitor as my main one is about to give up (missing horizontal lines etc etc) but until it does I was looking to take advantage of using 2 screens to avoid so much tab switching.

I am running both monitors in 1920x1080 (although the old one is 1680x1050 native) but whenever I try to use the Blueprint Editor 2 it is just a plain white box with no visuals at all. If I disable a monitor, as soon as the changes are made then it refreshes to being normal. Below is a list of things I have tried so far.

1. Clean install of the very latest nVidia graphics card drivers.
2. Running the old monitor in native res of 1680x1050.
3. Opening Blueprint Editor 2 on single monitor then enabling the second monitor - this gives me the visuals of BPE2, but it doesn't function properly and if I try to drag it anywhere it is very laggy, like around 3 fps displayed of the movement being undertook - once again, no issue with slowness or moving when on a single monitor.

I am perplexed by this. I hava attached a screenshot, I fully expect abuse for the state of my PC desktop, but like my mucky side of the room - I know where everything is!

deltic009 wrote: I was looking to take advantage of using 2 screens

Matthew, I have been trying to run TS on 2 screens since I got RW in 2012.
Ive tried just about every idea I have had suggestd, even discussed it with card makers at major exhibitions.
NEVER worked.
Every other program I have is fine with two screens Except TS and FlightSim.
Windowed or full screen make no difference. So I have given up.
What you can do (with TS or FS) on the second screen is run a Map (or Google earth) tracking your position. Cheers John

Yeah but that doesn't address the kind of issue Matt Wilson is facing as he isn't trying to run the blueprint editor across two screens.... Just wants to have two screens attached to his computer and run the blueprint editor on one of 'm .... The symptoms are really, really, really weird here!!

I guess this can only be solved by DTG but I doubt they're willing to. I'm wondering if anyone else has issues like this.

I guess the only things you could try is to either have one monitor as your main desktop (and have taskbar only on that one) or running the blueprint editor inside a virtual machine that knows only a single monitor...

I don't know if there's a way to make it so that all seems one single screen for windows and don't have a double monitor setup at present to test with.

Good luck with it,

--Tim

I'm not really fussed about maps etc, I'm not looking for a use for the second screen as I already have that, the problem is with Blueprint Editor not functioning as it should it will stop me from using two monitors to speed up my workflow.

I've spoken to another member of Vulcan Productions that uses two monitors and he has no issues with BPE at all, so I'm really confused by it.

Different settings in Windows for how Windows addresses the monitors?

Which screen is set as primary screen?

What card does he (she) have?

Difference in version of .Net or MS VC++ runtime libraries installed?

Different version of Windows perhaps?

--Tim

I have encountered this issue before, not when using dual monitors (they've always worked fine), but when applying shaders.

Quick way to fix it is to remove the shaders temporarily, so presumably, if you remove one of the monitors (which would mostly likely be the recently added one) it should start working again, not ideal but a quick fix if you wish to get back to work.

If you are trying to run dual monitor TS (maybe you were as a test, using SoftTH), maybe you should remove that, it could be messing with it.

What happens if you drag the Blueprints editor window over to the other monitor Matthew?

gptech wrote:What happens if you drag the Blueprints editor window over to the other monitor Matthew?

It stays white regardless of which screen it's on, but what Albie said regarding shaders reminded me that I had a custom DeferredDirectional shader that enabled in game ambient occlusion rendering. Typically I have read this after replacing them for performance reasons (wanted to do 4K video on a not-really 4K capable machine) and I am yet to test whether it is fixed or not - due to eldest having some time recording videos for his YouTube channel (youth of today).

I shall update the thread with results when they are seen.