I have finally finished up some of the more urgent bugs like the crash when selecting trading routes, the glowing textures and the crashes on startup.
I can't say to 100% that they are solved because I only have so many computers to bug test the game on. These bugs were supposed to be fixed a lot sooner, but first the Christmas and the New Year preparations came in the way, then after that I had that vacation in Israel where I meet Ben.
Tomorrow I will release the next version which will mostly be a bug fix version, and today before I go to bed (it is really late here in Sweden right now...) I will see if I have the energy to solve some other bugs that has been reported.
BurningPet has also contributed with a new Rock texture, what do you think?
[IMG]replace_photbucket_link/NewRock2.jpg[/IMG]
And the launcher has gotten a new option where the user can choose what screen he wants to use when going fullscreen and not being only confined to the primary screen.
[IMG]replace_photbucket_link/LauncherOutput.jpg[/IMG]
I also tried to solve the issue with not being able to go fullscreen on a secondary graphic card. This was a really annoying issue and I had to turn to a gamedev community for advice: http://www.gamedev.net/topic/664696-unab...reen-mode/
The conclusion was that it isn't the game itself that gives the user the power to do this, it is in the GPU's own control panel. In my case I had to open up NVIDIA control panel in windows and choose Dwelvers.exe and add the NVIDIA card as primary card before I got this option. This can be a little annoying because there may be others out there complaining and saying that it is the code fault that it isn't working when it actually is windows fault. Well, we will see how it goes, if there are complaints about this in the future I will have to look into it some further, there are most probably a workaround.
Another thing that have been annoying me is that if the game closes expectantly with an error message it isn't always the case that the user have time too see this error message, especially when the game is running in fullscreen and the message gets behind the screen. I solved this dilemma by adding a message box when the game started the next time repeating the error.
[IMG]replace_photbucket_link/ErrorLog.jpg[/IMG]
So in this case with low memory it should be obvious enough to see why the game crashed the last time and what to do about it.
I can't say to 100% that they are solved because I only have so many computers to bug test the game on. These bugs were supposed to be fixed a lot sooner, but first the Christmas and the New Year preparations came in the way, then after that I had that vacation in Israel where I meet Ben.
Tomorrow I will release the next version which will mostly be a bug fix version, and today before I go to bed (it is really late here in Sweden right now...) I will see if I have the energy to solve some other bugs that has been reported.
BurningPet has also contributed with a new Rock texture, what do you think?
[IMG]replace_photbucket_link/NewRock2.jpg[/IMG]
And the launcher has gotten a new option where the user can choose what screen he wants to use when going fullscreen and not being only confined to the primary screen.
[IMG]replace_photbucket_link/LauncherOutput.jpg[/IMG]
I also tried to solve the issue with not being able to go fullscreen on a secondary graphic card. This was a really annoying issue and I had to turn to a gamedev community for advice: http://www.gamedev.net/topic/664696-unab...reen-mode/
The conclusion was that it isn't the game itself that gives the user the power to do this, it is in the GPU's own control panel. In my case I had to open up NVIDIA control panel in windows and choose Dwelvers.exe and add the NVIDIA card as primary card before I got this option. This can be a little annoying because there may be others out there complaining and saying that it is the code fault that it isn't working when it actually is windows fault. Well, we will see how it goes, if there are complaints about this in the future I will have to look into it some further, there are most probably a workaround.
Another thing that have been annoying me is that if the game closes expectantly with an error message it isn't always the case that the user have time too see this error message, especially when the game is running in fullscreen and the message gets behind the screen. I solved this dilemma by adding a message box when the game started the next time repeating the error.
[IMG]replace_photbucket_link/ErrorLog.jpg[/IMG]
So in this case with low memory it should be obvious enough to see why the game crashed the last time and what to do about it.