• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
As requested by the QA guy, you need to post this.

Also, please attach your Dungeonland logs. They are located in you Steam folder, ...Steam\steamapps\common\Dungeonland Beta\dungeonland_Data\output_log.txt

This log is overwritten every time you restart the game, so make sure you save the log after you quit the game when you have run into this bug.

You and your friend (Separate his log from yours though)
 
Does the same thing. There's so much text, and it says the same stuff over and over. One example is:

(Filename: C:/BuildAgent/work/14194e8ce88cdf47/Runtime/Network/NetworkManager.cpp Line: 1678)

Couldn't perform remote Network.Destroy because the network view 'AllocatedID: 14175' could not be located.

(Filename: C:/BuildAgent/work/14194e8ce88cdf47/Runtime/Network/NetworkManager.cpp Line: 2460)

View ID AllocatedID: 14993 not found during lookup. Strange behaviour may occur

(Filename: C:/BuildAgent/work/14194e8ce88cdf47/Runtime/Network/NetworkManager.cpp Line: 1678)

Couldn't perform remote Network.Destroy because the network view 'AllocatedID: 14993' could not be located.

(Filename: C:/BuildAgent/work/14194e8ce88cdf47/Runtime/Network/NetworkManager.cpp Line: 2460)

View ID AllocatedID: 15002 not found during lookup. Strange behaviour may occur

(Filename: C:/BuildAgent/work/14194e8ce88cdf47/Runtime/Network/NetworkManager.cpp Line: 1678)

Couldn't perform remote Network.Destroy because the network view 'AllocatedID: 15002' could not be located.

(Filename: C:/BuildAgent/work/14194e8ce88cdf47/Runtime/Network/NetworkManager.cpp Line: 2460)

View ID AllocatedID: 14614 not found during lookup. Strange behaviour may occur

Another is:

HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
Skipped rendering frame because GfxDevice is in invalid state (device lost)

(Filename: C:/BuildAgent/work/14194e8ce88cdf47/Runtime/Misc/Player.cpp Line: 1608)

HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
Skipped rendering frame because GfxDevice is in invalid state (device lost)

(Filename: C:/BuildAgent/work/14194e8ce88cdf47/Runtime/Misc/Player.cpp Line: 1608)

HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
Skipped rendering frame because GfxDevice is in invalid state (device lost)

(Filename: C:/BuildAgent/work/14194e8ce88cdf47/Runtime/Misc/Player.cpp Line: 1608)

HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
Skipped rendering frame because GfxDevice is in invalid state (device lost)

(Filename: C:/BuildAgent/work/14194e8ce88cdf47/Runtime/Misc/Player.cpp Line: 1608)

HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
Skipped rendering frame because GfxDevice is in invalid state (device lost)

(Filename: C:/BuildAgent/work/14194e8ce88cdf47/Runtime/Misc/Player.cpp Line: 1608)

HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
Skipped rendering frame because GfxDevice is in invalid state (device lost)

(Filename: C:/BuildAgent/work/14194e8ce88cdf47/Runtime/Misc/Player.cpp Line: 1608)
 
Wrap it using
Code:
 tag, click "Go Advanced" to access it.

Few examples on this thread: [URL="http://forum.paradoxplaza.com/forum/showthread.php?662146-Lag-and-low-fps"]http://forum.paradoxplaza.com/forum/showthread.php?662146-Lag-and-low-fps[/URL]
 
Same issue here @ the laggy gameplay. My personal guess is that this is related to V-Sync, which we cannot switch off. It's definitely not related to GPU or HDD performance.
 

Attachments

  • output_log.txt
    106,2 KB · Views: 368
If you think it's V-Sync, try and force disable it. NVidia way http://prntscr.com/qyf3y

That screen shot has it as let the application decide, is that meant to be set as off?

Tried to turn it off on my AMD card, it just ignores it :(, stays at 60fps. Drops in a big group, I hoped if I dropped the vSync it would go over 60fps and tax my card a bit more.
 
Last edited: