Known Issues and possible solutions (copied from forum.paradoxplaza.com)

! Logging in/out a lot of different profiles, especially during games, causes problems of different kinds. This might block you from progressing in the game.- Don't change profile in game and preferably log in all profiles that are to be played while in the start screen.

We are monitoring the connectivity issues and there are two known issues right now.First, the Steam invite feature might not work if your UDP port 25002 is publicly visible/mapped.Second, in certain circumstances, the number of players is incorrectly reported in the server browser, thus leading to a connection failure.Please assert that these issues do not apply to your case. Both will be fixed in a future (soonish) patch.

Also, please head over to forum.paradoxplaza.com and post a copy of your output_log.txt file, present in your game data folder along with some info of the game like: Server or Client? OS? . It will further help us debug the problem.

Cheers,Poindexter

! If you are in the middle of reviving a character and that player leaves the game or signs out, your character will be stuck and you will have to quit and rejoin the game.- No known solution at the moment

! Sometimes extra bots are spawned when players hotjoin an ongoing game.- Might be avoided by playing with the same people all the time and to use the hotjoin function as little as possible.

! In some cases players and/or bots might be knocked outside the playing area of Dungeonland where it is impossible to get back in. The exact cause is unkown- Loose or win the game and the character will be spawned inside the game again. Also quitting and rejoining spawns the character anew.

! Disconnecting and reconnecting controllers/gamepads is not recognized by the game. This causes an issue that the game will think that one of the controller spots are already occupied when they really aren't.- Make sure not to disconnect any controllers while playing the game!

! I'm having lag issues!- The game does not run on dedicated servers. If you have lag there is not much we can do. Try to find a game hosted closer to your location.

! I can not start the game, it says that I'm "missing an executable file"- Right click Dungeonland in Steam and remove local content. Then try re-installing. That should work.

Possible workaround: Change the compatibility settings of dungeonland.exe to Windows XP SP2. It seems to help some people.

- Go to Dungeonland in your steam directory on your computer. Typically found at: C:\Program Files (x86)\Steam\steamapps\common\Dungeonland- Right click dungeonland.exe and select "properties"- Click the Compatibility tab and check "Run this program in compatibility mode for:" and select Windows XP (Service pack 2) in the dropdown list below- Click "Apply" and then "OK". - Start the game

! Cannot bind hotkeys, getting the message "You must assign keys to all commands first."- You will not be able to bind hotkeys if you try binding any of the buttons W, A, S, D or Esc to any of the following functions: Pause, In-Game Chat, Evasion, Weapon Skill, Potion Skill, Use/Grab/Revive, Attack or Class Skill.

! The game does not start at all.- It seems this is an issue that occurs with certain Anti Virus software and firewalls. Try disabling these (don't forget to turn it on after) and give it another go to identify the problem. You can also try adding Dungeonland to your safe lists in any security software you may be running. Read more about these problems here: http://forum.paradoxplaza.com/forum/showthread.php?662160-Will-not-start-(not-exe-related)

! Following the patch, my game is crashing repeatedly- Try re-installing completely. Meaning that you "Remove all local content" through steam and then manually delete any files/folders remaining in the Steam and User directories.

have to mention, that the frame issues are only in playermode not in DM Mode. Played the game in a private match and figured out, that i got a hugh FPS drop in Player Mode, espacially when there are mines or missles about to explode or something is spawning right in front of me.

How to obtain the game log! This can be found in your steam directory (typically C:\Program Files (x86)\Steam\steamapps\common\Dungeonland\dungeonla nd_Data) called output_log.txt can be very helpful!

How to make a dxdiag log (in Windows Vista and 7, if you are running XP you probably have the problem right there):* Click on your "Start" button.* Write dxdiag in the search field.* A box called "DirectX Diagnostic Tool" should open.* At the bottom of this window, you will find a button called "Save All Information".* Click this button.* A box will pop up prompting you to save a file called "dxdiag.txt"* Save this file to your "Desktop".* Now you should see a text file called "dxdiag.txt" sitting on yourWindows desktop.

I used some of my debugfu to take a quick look and found that the game has atleast one memory leak that is possibly related to the second issue.

The second issue is that you are constantly polling for new gamepads. And in a lot of hardware configurations(usually involving gamepads that are not standard wired x-box pads) this generates a lot of unneccessary hardware interrupts and makes the plug & play service work serious overtime usually slowing down the whole OS and definedly slowing donw the game. This is a higly educated quess as a lot of game studios make this same mistake.Most of the time this can be detected by looking in windows 7 performance manager that is found under performance in windows task manager. You usually see System Interrupts using a lot more CPU than normal and if you tag svchost(DcomLaunch) and look into the services list the plug&play service is using a lot of CPU. Also note that the problematic gamepad does not even have to be plugged in. Windows keeps a record of all plug&play devices ever installed on the system so it can load the drivers faster when the device is actually plugged in. And when you ask the plug&play service for a list of game controllers it asks all these drivers if the game controller is plugged in. And a lot of third party game controller drivers are really really slow in responding to this call making this problem even worse.

Also when analysing the waitchain you can see that most of the time you are waiting for network I/O even if you are in the main menu. I don't have much experience in unity based programs so I don't know if this really is an issue as it could be a side effect of constantly polling the gamepads. And as I don't have access to the source code I can't use a proper profiler to confirm if it really is waiting for network I/O that much. But usually when taking a random sample of programs waitchain it should most of the time report that it is not waiting for anything. This game however almost always seems to be waiting for network I/O to finish so there is definedly something going on but this could also be a side effect of the second issue.

have to mention, that the frame issues are only in playermode not in DM Mode. Played the game in a private match and figured out, that i got a hugh FPS drop in Player Mode, espacially when there are mines or missles about to explode or something is spawning right in front of me.

Seeing as in DM mode controllers are not supported this further leads me to believe that my highly educated quess is right.

Edit: Just noticed that If you play a little in DM mode(where the game runs just fine) and then go into player mode it seems to slighly improve things. I can get almost 30fps now intead of 5.Edit2: The memory leak still appears to be happening so it might be a separate issue. But I suggest trying to fix the issue with the controllers first and see if that fixes everything.

In some cases players and/or bots might be knocked outside the playing area of Dungeonland where it is impossible to get back in. The exact cause is unkown.^^^^Thats an easy work arround till you fix the problem, the fucnction that moves the characters should have a bounds check on it, if you detect a character is out of bounds, kill it if its a bot, randomly place it in a legal space nearby. Players will just think its lag. Then you can work on how to fix the problem at your lesure.