Getting black screen when loading into POE from ship since this hotfix.

[Neroo01]

Never happened to me since this hotfix, but what happens is when I loading into poe I get stuck in a black screen for 20 seconds and then POE loads with a host migration and kicks me back to ship.

 

Happening during Eidolon hunts(charging vs early) and normal games.

Edited January 4, 2019 by Neroo01

[sam686]

A few possible problems...

1. Slow Shader compiling and shader cache for graphics card. For AMD radeon settings, make sure shader cache is AMD Optimized, not off.

2. Clan emblem freeze bug. There is a log file called "ee.log" that might show some information, such as if it took more then 20 seconds to load clan emblem from the server, freezing the game for more then 20 seconds, then unfreezes and will lose connection to squad.

 

[Neroo01]

13 hours ago, sam686 said:

A few possible problems...

1. Slow Shader compiling and shader cache for graphics card. For AMD radeon settings, make sure shader cache is AMD Optimized, not off.

2. Clan emblem freeze bug. There is a log file called "ee.log" that might show some information, such as if it took more then 20 seconds to load clan emblem from the server, freezing the game for more then 20 seconds, then unfreezes and will lose connection to squad.

 

Found this line in EE when loading into POE maybe causing the freeze.

94.300 Sys [Info]: Generated 10 deps and 132 exclusions in 233ms (vetting took 233ms)

[sam686]

233ms is only 0.233 seconds, it must be something else that might cause it.

A hint is to look at the number at the left Also look for "connection timeout" part in the log and several lines above it.

 

Note, log might show information that should not be shared publicly, such as IP address (4 numbers with dots in between) and other player's usernames.

Old logs might already be lost by restarting game, so nothing can be seen if too late to look in it or copy log files.

[sam686]

On 2019-01-03 at 9:19 PM, Neroo01 said:

when loading into POE

Probably too small amount of RAM. Does the loading get slower and worst when going to Orb Vallis?

 

User have sent me a full log file and I can see some performance problem on the computer itself.

Processor: Intel Dual-HT Core i3-4010U 1700MHz

Physical Memory: 2GB / 4GB free (problem)

Operating System: Windows 10 [64-bit]

Found D3D adapter 0: Intel(R) HD Graphics Family (D3D_FEATURE_LEVEL_11_0)

 

The most likely problem of slow loading is only having 4GB total RAM, and a slow HDD. Upgrade to more RAM, preferably 16GB of RAM is good enough (DDR3 so-dimm for this CPU) and/or upgrade to faster and quiter SSD (Solid State Drive)

Old intel graphics might be a possible problem as well. The problem with most laptops is GPU (graphics processing unit) cannot be upgraded and will require a whole new computer.

 

My computer do have AMD Ryzen 2400g, 32GB DDR4, windows 10 64 bit, with a motherboard Asus Prime B350 Plus. Probably should go with different motherboard with DisplayPort + HDMI, because VGA on my motherboard is kindof buggy and DVI-D single link limited to 1920x1200 60hz.

[ArgusXen]

I'm often getting crashes while playing, usually in the same few situations. The logs are usually all different right before the crash, but they all end with a "GPF" error.

Most commonly happens in:
- Plains of Eidolon
- Earth Void fissure missions (including Sealab tileset)
- Orokin Sabotage (I just can't complete the Stribog node, multiplayer or solo.)
- Ceres - least common, but sometimes repeatedly crashes right after joining a multiplayer session. Once crashed in the middle of a solo mission, too.

When it tends to happen:
- Several seconds after joining a multiplayer session - or, in case of PoE, right after entering the plains (usually at Dawn, Dusk, during rain, or with an active bounty, usually right after Lotus marks the first objective).
- At some point during a mission after firing a weapon, using ability, picking up a rare resource (noticed with Grokdrul in PoE, log indicated it tried to load the item image before crashing), mounting a Dargyn in PoE (only had it crash once) or a new enemy spawning (judging by log).

Changing graphics settings to any level seems to have no effect on the crashes.
Verifying cache integrity and optimizing it didn't help. (Recently switched to SSD drive - didn't help either).

Well, I'm playing in Linux with Wine+DXVK and the latest NVIDIA drivers - I know it's not an officially supported system, but from what I've read, the Windows people have all the same crashes in similar situations. (also, the crashes only happen occasionally, and the game runs pretty well all in all).

My specs: AMD FX-6300 6-core processor, 8GB RAM, NVIDIA GTX 1050 2GB.

 

Edited January 5, 2019 by ArgusXen

[Neroo01]

Temporary Solution was DX9 32/64 bit.

 

This will be changed as DE has stated to remove DX9 & 32bit from warframe.

 

Edited January 6, 2019 by Neroo01

[ArgusXen]

Just to add to my previous post, I've been playing for 3 days without any crashes, while not doing any missions I listed above.

Then got a one-off crash today during a Saturn multiplayer mission (invasion sabotage).

Tried the Plains of Eidolon after that. Crashed 2 times during a bounty mission. Tried switching to 32-bit mode (with DX11) - performance degraded, but no crashes (doesn't strictly mean it's because of 32-bit mode - I've played in PoE for extensive time before, with no crashes too. Still, it was a >50% chance to get a crash while there).

Here are some last lines in the logs from PoE crashes:
While escorting a hijacked drone near a Grineer base and starting melee:

Quote

2130.570 Sys [Info]: Ragdoll::CommonInit() 2.1ms
2130.853 AI [Info]: ENCMGR: Encounter /Lotus/Types/Gameplay/Eidolon/Encounters/LootCrateSpawnWilderness started at /Layer255/Layer1/Layer94/LootCrateWildernessEncounterHint6 at pos [(635.229, -1.09718, -372.662, 0)]
2130.875 AI [Info]: ENCMGR: Encounter [/Lotus/Types/Gameplay/Eidolon/Encounters/LootCrateSpawnWilderness] has completed on hint [/Layer255/Layer1/Layer94/LootCrateWildernessEncounterHint6] at pos [(635.229, -1.09718, -372.662, 0)] status ES_NONE

Right after encountering the objective and attacking in melee:

Quote

1838.636 Script [Info]: Idle -> combat
1839.470 Script [Info]: CheckAdvanceToNext taking/Lotus/Sounds/Dialog/LandscapeMissions/Rescue/DResPrimedLotus
1839.540 AI [Error]: Timed out waiting for Melee to Start

Both followed by "Error [Info]: GPF"

PS: Just had a successful extended solo run on PoE with no crashes. 64-bit version. Morning->Day. Did a bounty, an incursion, and some mining. The difference from before is that it wasn't raining.

Edited January 9, 2019 by ArgusXen