- Joined
- Feb 26, 2022
- Messages
- 947
- Reaction score
- 1,646
- First Language
- English
- Primarily Uses
- RMMV
You can check the size of the screen by going to the plugins and checking the Community_Basic plugin that comes pre-installed in all new RM projects. Otherwise, if you are using Yanfly's core plugin you can also change the resolution there. If you have neither of these, then it will use the default resolution (which I believe is 480p, 4:3). Not 100% sure on this, but I do believe whatever the default resolution is, it is a perfect integer of of the tiles, so there will be no rounding problems.
MV in particular seems to have some problems with high refresh rate monitors (see the link in my signature). The problem may be related to your monitor displaying 75fps. 75 is sort of a weird number. While I am aware that there are lots of monitors for sale that are clocked at 75, it's neither really reaching the territory of "high refresh rate", nor is it a standard integer of common video speeds.
The engine likes integers of 30; 30, 60, 90, 120. (well, technically, it only likes 30 and 60 and above that it will crash - again, see link in sig). So there may be a different kind of rounding problem happening because of the odd refresh rate.
To test if this is the case, first let's manually cap the frame rate. In the link in my signature I go over how to do this in detail. In short; access your GPU's control panel, select nwjs.exe or game.exe and apply a frame rate limited to the application. Make sure to click apply to save changes. Now test to see if the game works.
Doing so has the potential to introduce other unwanted graphical behavior, but we aren't really looking for that, all we are testing for is whether or not the camera jitter is fixed. If so, then we have determined it's a frame rate problem and then we can start looking for a vsync plugin (FPS synch is not vsync). Whether it fixes the problem or not, after your testing you can remove the fps cap (unless you want to keep it)
I'll be willing to check the project myself, though I cannot program anything for you.
If you do decide to commission someone for a fix, keep in mind it's not really as simple as farting out some code. I suspect the thing that is going to take the most time is not the code itself, but actually diagnosing what is causing the behavior in the game. And depending on the cause of the behavior, it may not be a simple fix as it might not actually be an error in the code but an intended effect to patch out an even more unwanted behavior.
Anyways, if you do go down that route, comissioning shouldn't happen in this thread. You will need to go to the Classifieds section and submit a commission there (for for mods to approve it) and hope someone is willing to take on your project.
MV in particular seems to have some problems with high refresh rate monitors (see the link in my signature). The problem may be related to your monitor displaying 75fps. 75 is sort of a weird number. While I am aware that there are lots of monitors for sale that are clocked at 75, it's neither really reaching the territory of "high refresh rate", nor is it a standard integer of common video speeds.
The engine likes integers of 30; 30, 60, 90, 120. (well, technically, it only likes 30 and 60 and above that it will crash - again, see link in sig). So there may be a different kind of rounding problem happening because of the odd refresh rate.
To test if this is the case, first let's manually cap the frame rate. In the link in my signature I go over how to do this in detail. In short; access your GPU's control panel, select nwjs.exe or game.exe and apply a frame rate limited to the application. Make sure to click apply to save changes. Now test to see if the game works.
Doing so has the potential to introduce other unwanted graphical behavior, but we aren't really looking for that, all we are testing for is whether or not the camera jitter is fixed. If so, then we have determined it's a frame rate problem and then we can start looking for a vsync plugin (FPS synch is not vsync). Whether it fixes the problem or not, after your testing you can remove the fps cap (unless you want to keep it)
I'll be willing to check the project myself, though I cannot program anything for you.
If you do decide to commission someone for a fix, keep in mind it's not really as simple as farting out some code. I suspect the thing that is going to take the most time is not the code itself, but actually diagnosing what is causing the behavior in the game. And depending on the cause of the behavior, it may not be a simple fix as it might not actually be an error in the code but an intended effect to patch out an even more unwanted behavior.
Anyways, if you do go down that route, comissioning shouldn't happen in this thread. You will need to go to the Classifieds section and submit a commission there (for for mods to approve it) and hope someone is willing to take on your project.