John - NEXFER

Could this be related to the higher than normal CPU usage of the Server Monitor application? Some users are reporting twice the CPU usage from the monitor, as there is from the server - 50% monitor and 25% server. It seems like it should really be the other way around!

Hi there, yes at the moment, it seems impossible to host a dedicated server and play the game on that same machine, as they are both using the Ylands.exe for server / game. If you are hosting from your game machine, the only current way is via the in-game multiplayer options - though the server will shutdown when you exit game. They may change this at some point, I'd guess when it hits Steam, but I don't know. At the moment at least, the dedicated server requires a separate machine to host from, a VPS, Dedicated Server or your own second PC / Laptop. If you try to run them both on the same machine, you will encounter the black screen with sound only. I have no idea if this is intentional or a bug though.

Nice! That should keep you going well beyond the current 10 players limit.

Yeah these things happen with me as well, though I haven't ran into the timers one yet, will add it to the list in the original post. I've shut down my server for now, till the crucial stability issues are resolved. Not much point in trying for 24/7 at the moment!

For flying you can use the propeller pack with /additem propeller_pack (needs admin or single player).

Added to the list, I'm not sure in what instance your server monitor (ServerMonitor.exe), is using more CPU % than your server (Ylands.exe)? Mine is running at between 25-30% CPU on Ylands.exe and 5-10 % on ServerMonitor.exe, though this could all change depending on how many people online I guess. At the moment nobody is online, so this would be the floor rate, rather than the ceiling. I don't know how much it scales up with players online, I will monitor it though. Likewise, the Ylands.exe is consuming 2,012,356 KB (2GB) of RAM and the ServerMonitor.exe is comsuming 212,796 KB (0.2GB). Does it maintain your 50% / 25% ratio for any length of time? Or is it spiking up to that and dropping down? And yes, I've noticed a considerable performance hit in-game, a lot of new freezing and lag spiking while playing since the update it seems?

I've updated the original post with a more structured approach, this should help keep a handle on some of these bugs until they get fixed.

Yes, if you're playing GTA V? Then you should be able to play this without issues really. I'm not sure what to suggest at this stage, however, if it was me, I would likely do the following (if you haven't already). Uninstall the game, navigate to C:\Users\USERNAME\Documents and delete the Ylands folder. (Or the equivalent location for windows 8) Reinstall Ylands, see if it's fixed. If not, I could only suggest something like a driver assistance tool, I personally use Driver Booster, because they constantly release free "Pro Version" keys on YouTube, just search on there for "Driver Booster Key". The advantage of this is it can check for up-to-date drivers for all your devices, and searches for latest dependencies for games as well, this saves me a lot of time and hassle. I use it a lot on fresh builds to save sourcing all the drivers from manufacturers and get the machine game-ready, I never have any issues but I've been using Windows 7 and not 8.

Do you have any issues playing any other games of similar type? Does your system meet the minimum specifications etc? CPU, RAM, GPU / Graphics Card?

I would imagine you are likely missing a required dependency that either Ylands.exe or YlandsLauncher.exe needs to function correctly. Windows update should fix this, or you could attempt to uninstall Ylands and reinstall it, as I'm not certain if these dependencies are included in the game files at this early stage, this might do nothing. A developer could likely elaborate further on what could be missing or needing updating. In the meantime, you could potentially look to see if the following generally used dependencies are installed and/or updated on your machine (or just run windows update), though I have not much clue as to which if any of these could be required. - Latest Graphics Card drivers - Can be sourced from the manufacturer website of your device likely either AMD or NVIDIA. - Latest DirectX updates - A guide can be found from Microsoft. - Latest C++ Redistributables - A selection can be found from Microsoft. - Latest .NET Framework - .NET 4.0 or perhaps .NET 4.6.2. - Latest XNA Framework (not sure if needed at all) - Can be downloaded from Microsoft. Failing this, it may prove useful to provide the version of Windows on your machine, and system specifications, to allow further diagnosis. Also, the developers often ask which DirectX version are you using? And inform you that Ylands requires version 11.1, though version 11 seems to work for me (unsure if the .1 shows up anyway in dxdiag). You can find this by typing "dxdiag" in to the Windows Run / Search box in the start menu, and pressing Enter.

Yes as far as I know, you need a copy of the game to run the dedicated server, and as far as I know, you need to log in to your account to load the dedicated server through the Ylands Launcher. You can also log in and play on this same account, so you only need one account to host and play on. You can set up the target section like so - You can find your external IP via Google, by asking it "what is my ip". I'm not sure if you need to port-forward for Ylands, to allow incoming connections that reach your Router, to be directed through to a PC within your home network, but it seems very likely, so I've done this for my server. The basics of port-forwarding can be found readily available on the web, however, to summarise for you - Connect to your Router, usually something like http://192.168.0.1/ in your web browser Log in to the admin account for your Router, usually this information is written on your Router somewhere, and should likely be changed from the default once you log in to it. Your Router will likely have some options for port-forwarding in one of the advanced menus, have a browse and locate it, or Google your Router's make and model for a guide, the make and model should likely be written on your Router near the default username and password. You will need to direct all incoming connections with port-forwarding, on the port you have chosen for the server in the server monitor, and direct them to the internal IP of your computer that is hosting the server. To find that PC's internal IP, you can likely locate this information on your Router, as this device assigns internal IP's to devices that connect to it, you can also make a reservation for this internal IP, and the MAC address of the server computer, that way, if the internal IP is ever refreshed somehow, your server computer will retain it's internal IP address, and thus not break your port-forwarding rules. You can also open a Command Prompt on Windows by typing "cmd" in to the Windows Run box, and hitting enter. Once the CMD is loaded, you can simply type in "ipconfig" and it will reveal various network information regarding that computer on the network, including the computers internal IP - something like 192.168.0.* Good luck with your server!

1) already connected clients experience a lag type freeze up when another player is connecting / disconnecting - I can confirm this happens on my server as well, and it is quite noticeable, usually a few seconds of immobilisation. 2) entire server freeze up - I can confirm this as well on my server, rebooting seems to be the solution. However, I have to completely shut down and restart the server approximately less than every 12 hours, as I check it before I go to sleep, and when I wake up and check again it has hung (unable to connect, unable to shut down server via server monitor - indefinite "stopping"). 3) save file corruption - I've only had this happen the one time so far, but it is likely to happen again at some point as it happened to us within 30 minutes or so of play. The current save file that I'm using has not repeated this issue yet though. Another glitch / bug is that if you sail a large ship over top of a shark swimming in the water, the shark will end up stuck on the deck of your ship, an easy way to go shark fishing!

The joys if boredom! fits well haha

So, we've now encountered an issue whereby after a while, the server hung and we had to disconnect, upon restarting the server and reconnecting, we both were unable to load back in to game, becoming stuck on "Downloading game data from the server" or "Recalling buildings". I created a new save within the Server Monitor and I'm able to log in to it just fine, however, we have thus lost our progress and wouldn't want to keep going round in circles! Here is the affected save game file - YLANDERS_UK_DEDICATED.zip Here is the server log - output_log.txt Here is the client log - output_log.txt Also worth noting, you can load this save game file just fine in single player mode, it's just trying to connect to it via the dedicated server that is an issue.

Ah, that's no good, I noticed a lot of people connecting and disconnecting last night / this morning, I just assumed they weren't talking, but perhaps they were stuck too I've rebooted it anyway and I'm now online!

I've fixed my issue it seems, I took the following steps, and it seems likely that this was either a save game issue, or a port issue. I uninstalled and reinstalled Ylands on both client and server machines, deleted all the user data in My Documents (saves etc) on both PC's. I then created a new save game on the client PC and copied it over to the server PC, however, last time I did not delete this save game file from the client PC, this time I deleted it, so that only 1 copy of this save could be found, on the server PC. - This could have been the issue, though unsure. I then noticed in the log files that the client was trying to connect to the server on "192.168.0.3:65534", so I changed the local port to 65535 and external port to 65534, as it seemed to be requesting this port and not the port that I had chosen for it (28000). I then booted the server and tried to connect with the client, and success, I logged in just fine! So, it seems like my issue was either save game file related, or port related, or something else related that was fixed by reinstalling Ylands. Likely not a bug but a config issue then.

So we've narrowed down the issue to connecting via LAN, which effectively means I can't host a server and play on it unless it's hosted remotely on a VPS or Dedicated Server. Other players can connect just fine, however, when I try and connect from within my own network (192.168.0.11 connecting to 192.168.0.3), the client hangs on "Establishing Connection" with these errors in the log file - [net] connect attempt: endpoint=[EndPoint 192.168.0.3:65534 | 13882345864254521342] token=requestId=0b55b775-6ab3-4a66-b9df-df763131bdb6 bohemiaId=b4a9e6cf-8b67-4c8c-a840-618e4ab0e950 password= (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51) [net] failed to connect endpoint=[EndPoint 192.168.0.3:65534 | 13882345864254521342] token=requestId=0b55b775-6ab3-4a66-b9df-df763131bdb6 bohemiaId=b4a9e6cf-8b67-4c8c-a840-618e4ab0e950 password= Seems likely this is an easy fix if it is just a LAN issue, any ideas? output_log_server.txt output_log_client.txt

Feel free - http://steamcommunity.com/id/ylanders

Good to know, then it seems likely that it's a unique IP issue, or local network issue. As others can connect to it (like it was a VPS), just I can't within my own network! I did notice that my server had popped up in the server list, prior to me port forwarding to it, suggesting that it's connecting locally on LAN. I guess it is possible this issue is then located in connecting via LAN (192.168.*.*) and it seems to choose to do this by default on the server list (no option to change this manually?). Short of hosting my server remotely, I'm not sure what to try next! I have a 16gb quad-core sitting waiting to be used for this server, I'd hate to part with the monthly money to get a dedicated server with this spec, when I've got a better option! I also have a very fast net connection which I pay a bunch for, would hate to waste these already paid for resources and host it remotely!

Hi again, It seems that I am still unable to connect to my dedicated server, after the recent update and since updating both client and server versions. I now get stuck on the client, as soon as I click on connect to my server, from the server list. It hangs indefinitely on "Establishing Connection", however, there is no sign of connection from my self on the server monitor. I did see another player show up on the server monitor, then "connected" and shortly after "disconnected", but no sign of my self. Further, I was able to chat to this player in the server monitor window, using the SEND button, and they were online, so it's just me. If I click on cancel to abort "Establishing Connection", I am left with a slightly blurred out menu screen and nothing is clickable, so I have to force close the client. Current setup is much like the original above, I have two PC's and one of them has the dedicated server on it (gtx 750ti), and is port forwarded to on 28000. I launch the server monitor via the YlandsLauncher --servermonitor, and log in with my account (maybe I need two accounts for this?). Further, the exception is prompted and added to my firewall, when I choose the server name and ports, then click okay (local 28005, external 28000). I then connect to the game from my second PC (gtx 1060). I log in using the YlandsLauncher, and log in with my account (so this account is logged in twice now? Maybe issues?). I then run the game with "Play" and connect to the server via the server list, and get stuck. Did I miss something here? Do I need two accounts to achieve what I'm trying here (Two PC's 1 with server 1 with game)? I have tried running both server and client on the same PC, however it gives the black loading screen with sound only bug as mentioned in the original post. Attached are the server logs from the server machine, and the client logs from the client machine. I'd quite like to play on my own server! output_log_server.txt output_log_client.txt

Great! I've been looking forward to this update, will set up a dedicated server and get back to you with results! Thank you guys for all the hard work, that's a big list of updates / fixes.

Do you run the YlandsLauncher.exe and log in first? I get a black screen if I try and run Ylands.exe without logging in, maybe related?

Hi there, sometimes it can be as simple as to change your Power Settings mode to enable the more powerful graphics options by default. In: Start - Control Panel - All Control Panel Items - Power Options - Show additional plans - switch it to the "High Performance" setting. Other times, dependent on your dual graphics setup, you may have to enable this game to run with that card, within the software. AMD Catalyst Control Centre has some settings for this, likewise NVIDIA Control Panel should have some similar options.

Good way to lock a boat away in multiplayer, if the doors can be locked! Else some wondering vagabond could make off with yours jack sparrow style! A harbour would be another way if there was some kind of lockable "sea-gate" or draw-bridge! Could keep all your ships locked in your marina. Especially once it hits Steam... Geez, it will be: Start game, log in to a server, build a raft, steal a ship / kill the owner for his "booty"! It will be a pirate game for sure if no further options are added to manage this factor! Explore mode anyway. Could add an option to lock a ship? Though this seems unrealistic, perhaps you could remove the ships wheel and carry it with you! No idea really, I can just see a lot of Steam pirates in the future... *Edit* You could put the ships wheel and / or anchor inside a small room, with a locked door!

Funny enough, when I loaded back in to the game, I thought it had bugged out graphically all black, I then noticed the freezing cold warning pop up, and as the screen got lighter, I realised I was at the bottom of the ocean, still on my boat! It slowly rose to the surface, and I almost froze to death, but then it popped out at the surface and all was well! I think maybe this was something to do with exiting the game while still controlling the ships wheel. I guess you could just build new islands, it was pretty darn deep though! If the oxygen was ticking down (which it wasn't), I would have surely drowned.