Cursor Bug. Game is unplayable. Menu Bug too.

[evansgreen]

Hello. It would help to see someone actually saying: Hey, we're doing something.

Sorry for the rush, but don't forget that impatience is the first thing you should expect when you sell a 30 euros game that is utterly bugged and unfinished (I was going to use the word unpolished, but this one would be an euphemism), and with many of the features announced not implemented.

You're using us for beta testing, while you get some funds. I, myself, do not approve.

But I say this like you care.

[Novakiller]

Just thought i would add to this post, I'm currently experiencing this same issue on my main computer and trying to figure out how to fix it without a reinstallation of my graphics drivers. I'll post the machine specs this happens on, its a damn weirdo bug, I dont have any problems running the game on my other machine that i've been using since launch, it only messes up when i move the mouse even just a tiny bit.

Processor : AMD Phenom II X6 1090XT
Mobo : Asus
RAM : 8GB DDR3 1333 Gskill Ripjaw series
Graphics : X2 Nvidia EVGA GTX 560 Ti's in SLI Mode
PSU : BFG 1000WATT PSU
OS : Windows 7 Ultimate x64
Mouse : Roccat Kone +
Keyboard : Logicteck G10

Running at 1600X900 with the most recent nvidia drivers

[Novakiller]

Originally Posted by Joseph Visscher

Running the game in window mode may fix this.

Go to the games main directory. C:\Program Files\Reverie World Studios\Dawn of Fantasy what ever it is.

Inside you will find a file called local_saved_data, open it with notepad, Inside you will see
0

Change the 0 to a 1 so its
1

save the file and try turn on the game and tell us what effect it has.

Window mode is currently really buggy so you wont be able to play with it like that, but if it seems to work with your mouse moving around, it is most likely a hardware acceleration problem or a program conflict, do you have a program that changes how your mouse works do you have really odd mouse settings or something?

Anyways see if window mode is any different at all.

Just to quote this... there is no such file in my local games directory to change it to window mode

[SysOpPsyche]

Based on the symptoms your describing and my experience, I think I may know whats causing your problem and no you won't be able to fix it using that mouse, the problem is due to the update speed of that mouse and the game input handler code w/Windows requirements for applications running. That mouse is a High Performance Gaming mouse and I don't believe this game has an option to 'Disable Hardware Mouse handling' which is how most programs handle it (using program code nicknamed 'Windows Pacifier' function and more colorful names).

Don't suppose you have a cheap standard mouse to swap it out with and see if the game still exhibits the same behaviour?

The problem is most likely that Windows interupts applications everytime mouse input is detected (the first 100 lines of any windows program incorporates this) and the program has to handle it within a certain time or Windows kills the application. Problems occur when the update is extremely high and the code tries to actually process the input immediately or logging in a queue because that code has to be very lean and efficient or have a very BIG queue, if it doesn't then its usually not done before it gets another input update and basically causes the program to stutter/stall and if input is constant Crash because Windows kills the process thinking its hanged due to its inability to respond to this Windows Call. Most 'Windows Pacifiers' are simple code functions that take the input and overwrite a simple data structure and respond to windows to let it know everythings OK and then transfer it to the Actual input handler when the process feels its time to update that. Basically its one of those Pain in the Butt Windows things and really only typically happens with High Performance input in Heavily burdened applications. Simple to fix but often overlooked. Anytime you see an option setting thats 'Hardware Mouse ...' something thats usually what that setting turns on and off - doesn't matter whether your using DirectInput, Xinput or Windows handlers since they all report to & have to satisfy Windows or it kills the application thinking an error has occurred.

[Novakiller]

Interesting read and very technical. I was able to fix it by simply just swapping out a cheap old usb mouse, but i'd like to use my expensive mouse if i can with the game lol...

[evansgreen]

SysOpPsyche, all your post makes a whole world of sense, cause as you underlined, the game DOES work properly with crappy mouses in my computer, but ONLY with crappy mouses with low poll rate.

I'm very grateful for your interest and comment, and for sharing your knowledge about the topic, cause that gave me an idea... I'm gonna try to lower the poll rate of my mouse manually via the own mouse software and I'll try the game that way, I'll let you know if I can play that way.

Thanks again, you've been more helpful so far than any "technical support" which stopped answering a week ago...

[evansgreen]

BUG SOLVED THANKS TO SysOpPsyche

Solving process:

If you're having this bug, that means you're using a high performance mouse, which has at least a 500Hz polling rate (in my case was 1000, which is worse). Enter your mouse software, and look for the options to change the polling rate. In case is a razer, it will be "Tweak performance->polling rate" and lower it to 125 Hz.

You just turned your turbopro1337gamingmouse into a crappy one. BUT IT WORKS.

Again, I can stretch enough how grateful I am, and the rest of the people with the problem will be, now that we can actually play and enjoy the game. I can't help having a bit of a sour impression for the fact that it wasn't reverie studios the ones who gave a **** about it, but I'm very happy that it was solved in the end.

Thanks again, see you on the battlefield

[SysOpPsyche]

Good to hear it. Wasn't aware that some of the mouse could alter there 'polling rate'.

BTW the Developers are super busy patching, they are an Indie game company (meaning very small, low budget and typically understaffed/overworked). With the issues they are having this particular one wouldn't be a high priority since its more of a performance bug and compatibility issue thats affecting less users than their other issues are (figuring out whats causing a bug, is typically the hardest part).

They'll fix that soon enough they got bigger more severe problems. I know they read the forums a lot and this particular problem is as I said easy to fix and often overlooked.


Have fun.

[Novakiller]

very interesting, i'll have to check that out as well, i dont think my Roccat has that option in its software but i'll still check anyway, NICE FIND!!! what kinda frame ratse are you getting now?