Black Screen with mod v6 'Advanced Target Priorities EVO'

SealingSatyr511

This post is deleted!

nomads

Take care of yourself, good night

SealingSatyr511

@nomads not sure it was due to that. i prefer do a better control of any existing entries in gameprefs first.

The v7 contains several major fixes also.

SealingSatyr511

Thank you

SealingSatyr511

1.0.4 - Fix
-Added a test plan execution at startup to prevent GamePrefs issues
(version 8 in the vault)

magge

With v8 I do not get any black screen anymore, but unfortunately, I do not get any bottom build panel when I select any unit. (no other mods active).

warning: Error running '/lua/ui/game/gamemain.lua:OnSelectionChanged': ...\advanced target priorities evo\modules\settings.lua(802): perform arithmetic on expected but got nil
         stack traceback:
         	...\advanced target priorities evo\modules\settings.lua(802): in function `ApplyCoordinatesToPanels'
         	...\faforever\1\gamedata\lua.nx2\lua\ui\game\orders.lua(1881): in function <...\faforever\1\gamedata\lua.nx2\lua\ui\game\orders.lua:1875>
         	...\faforever\1\gamedata\lua.nx2\lua\ui\game\orders.lua(1675): in function `SetAvailableOrders'
         	...aforever\1\gamedata\lua.nx2\lua\ui\game\gamemain.lua(702): in function <...aforever\1\gamedata\lua.nx2\lua\ui\game\gamemain.lua:625>
warning: Error running '/lua/ui/game/gamemain.lua:OnSelectionChanged': ...\advanced target priorities evo\modules\settings.lua(802): perform arithmetic on expected but got nil
         stack traceback:
         	...\advanced target priorities evo\modules\settings.lua(802): in function `ApplyCoordinatesToPanels'
         	...\faforever\1\gamedata\lua.nx2\lua\ui\game\orders.lua(1881): in function <...\faforever\1\gamedata\lua.nx2\lua\ui\game\orders.lua:1875>
         	...\faforever\1\gamedata\lua.nx2\lua\ui\game\orders.lua(1675): in function `SetAvailableOrders'
         	...aforever\1\gamedata\lua.nx2\lua\ui\game\gamemain.lua(702): in function <...aforever\1\gamedata\lua.nx2\lua\ui\game\gamemain.lua:625>

SealingSatyr511

Ok.
can you share your GamePrefs "advancedpriotities" ?
and what is your current adapter resolution ?
Do you use a second monitor ? if yes, left or right display ?

magge

The 'advancedpriotities' entry in the Game.prefs:

            AdvancedPriotities = {
                windowHeight = 140,
                posY = 500,
                AttackConstructionLeftValue = 600,
                AttackOrdersLeftValue = 50,
                Preset = 'strogo1_1',
                FactoryConstructionRightValue = 1400,
                buttonLayoutSeparate = {
                    { },
                    { },
                    { }
                },
                windowWidth = 120,
                FactoryOrdersLeftValue = 50,
                posX = 50,
                FactoryConstructionLeftValue = 600,
                showSeparateWindow = false,
                lockSeparateWindow = false,
                hideAbilities = false,
                AttackConstructionRightValue = 1400
            },

Primary monitor: 2560 x1440 I use only one monitor for gaming. SC runs only on the main screen.

@SealingSatyr511 said in Black Screen with mod v6 'Advanced Target Priorities EVO':

Do you use a second monitor ? if yes, left or right display ?

Yes, bottom.

Edit: BTW, there is a spelling mistake:

For 'advancedpriotities' is the "r" missing; 'advancedpriorities'

SealingSatyr511

The gamePrefs is ok, yes it's advancedpriotities (without the r). It's easier for the dev to find in the gameprefs. it's native code of the old 1.1.

here is the code that fails :

-- check the serapate targeting window position
local separateWindow = import("/lua/ui/game/orders.lua").GetSeparateWindow()
local tableRez = mysplit(Prefs.GetFromCurrentProfile('options').primary_adapter,',')
if (prioritySettingsPrefs.posX > tonumber(tableRez[1])-207) or  
   (prioritySettingsPrefs.posY > tonumber(tableRez[2])-145) then    
        separateWindow.Left:Set(DefaultPosX)
        separateWindow.Top:Set(DefaultPosY)
        prioritySettingsPrefs.posX = DefaultPosX
        prioritySettingsPrefs.posY = DefaultPosY
        Prefs.SetToCurrentProfile("AdvancedPriotities", prioritySettingsPrefs)
        Prefs.SavePreferences()
        resetPosition = true
end

the condition is line 802 where the bug occurs.

but i m pretty sure it s due to resolution and coordinate retrieved from
Prefs.GetFromCurrentProfile('options').primary_adapter

it put the resolution 2560x1440 to a table, and i check the x and y position of the window.
This code is designed to prevent out of range position.

I don't reproduce this bug (i use a single monitor). the dual monitor may have an impact on how the resolution is retrieved by the game.
Does it take the resolution of the game ? or the windows system ? that's the key i think.

Be sure i m investigating this. I have a laptop with a dual screen (not the computer i run Faf), i m going to install faf on it and check how it works in debug. i must reproduce.

SealingSatyr511

I just tried with the same configuration, dual screen, 1 ON 2 ON, 1080p on both, the 1 up, 2 down. dual screen disabled in FA
I have zero issue, even with dual screen activated in FA

Can you have a try by switching off your second screen ? and put the code in comment to disable it ? (modules/settings.lua)

Is there other guy who experiment the same bug ?
Does it work well for you ?

Thanks for your help, it s a weird bug.

nomads

V8 has been tested under dual screen conditions, and the display mod is normal regardless of left-right, and up-down.

Conclusion for reference:

It seems that only the main screen has a UI toolbar
It is recommended to set your preferred screen as the main screen in the system settings before playing the game; The relative position of the screen doesn't matter, just adjust it according to personal habits.

SealingSatyr511

Only main screen have UI toolbar yes, it s the native behavior.
So Nomads, you don't have issue if i understand well.

nomads

yes，thank you.

SealingSatyr511

i don t like this kind of bug, because something is wrong somewhere, maybe in the adapter code of the engine itself.. i don't know.
But i would like to find a way to prevent this. It should not be.

nomads

About multi monitors，I think it may not be a problem with your mod, but rather with the player's hardware configuration and system settings.At present, I feel that everything is ok while using version 8.

SealingSatyr511

it seems the adapter code is weak.
I tried with very low resolution and 200% scaling, the lobby is broken. i must delete the gameprefs to recover a good display even in FAF lobby.

i switched the 2nd monitor to primary. It works in that mode too.

SealingSatyr511

magge, what scaling do you use ?

SealingSatyr511

magge, you can backup your GamePrefs files and delete it to force the game to create a new one from scratch and try again.

SealingSatyr511

in your gamePrefs :

            primary_adapter = '2560,1440,60',
            SSB2_Auto_Toggle_Mass_Column = true,
            SSB2_MessageWhen_SharingUnits = true,
            SSB2_MessageWhen_SharingEngy = false,
            secondary_adapter = 'disabled',

maybe your primary-adapter is disabled, and all the good values are on the second adapter.
It could explain why it return nil when i check the primary_adapter. Normally is it not possible by logic, but your may have an old GamePrefs with values that should not be. It depends on how the game detects your screens and how it decides what is primary for itself, and paint the UI on.

if it s due to that, i can fix it but it s not a normal situation or i did not understood how the engine works with adapters.
Reseting the gameprefs may be the solution for this strange behavior.

magge

I can pinpoint my issue to the state of the in-game window.

If it is set to 'windowed' (does not matter which resolution) the bottom build panel does not show up.

As soon I switch to full screen (again, does not matter which resolution, even 800*600 works now) the build panel shows up. I do not even have to restart SC to reproduce that.

Is it possible to fix that behaviour?