After reading the complaints here I'm still going to buy this game b/c I believe in Larian and that they will come through and I want to support studios like this so they can produce more games in the future. But being a developer myself I really do not understand the 30 FPS cap. I understand if 30 FPS is the minimum or worst case scenario or even 45 FPS but I cannot understand it being the maximum.
Anyway, I can see why the 30 fps issue is an issue for some players and we have been working on it. While it may look as a simple thing (I thought so too initially), for some reason removing the lock causes race conditions to appear. Essentially a race condition is when two threads in a piece of software are waiting for one another to complete, causing a deadlock. They are notoriously hard to debug because it's very hard to reproduce them. Over the last couple of weeks a number of engineers have been working on it, but unfortunately they aren't ready with their work yet. Personally the 30 fps lock doesn't bother me, but knowing that it might trouble some people, we'd hoped to have something ready in time to help them, but that just didn't work out, and at mastering time we decided to remove the option to remove the lock because of the problems that might otherwise appear. We also couldn't afford to have those engineers spend all their time on it, because there were a thousand other things that needed to be sorted out.
Having worked with threading and race conditions in Windows I can feel your pain b/c it is not simple and your code does very strange things that are extremely hard to track down and debug. However it appears to me that the initial design of the system might have been lacking b/c these race conditions should have been at least recognized or anticipated. How hard would it be to simply remove the offending threads and linearize the process instead of trying to separate the tasks into separate threads? I'm not suggesting linearizing the entire game but perhaps the portions that are causing troubles could be.
Thank you so much for recognizing the complaints about the 30 FPS instead of attempting to place blame. It also gives me hope for this game since it appears the 30 FPS might have been achieved by simply wasting cycles (Sleep()?) or using a timer somewhere to slow the system down. Once you fix the race conditions I look forward to these temporary fixes being removed. I can certainly understand your position in releasing the game in a stable state instead of attempting to push out an unstable game that would crash constantly and give it a terrible reputation.
If I had not read your response I probably would not have purchased this game b/c I was afraid the game was permanently locked to 30 FPS.
Sorry for altering my post...my original was posted before I read the post from Larian about the threading. The threading issue definitely hits home with me so I can understand the complexity of the issues at hand.
