Nice! Is it on the website already? Will do a test run to make sure it works..
Sure, i updated it on ftp! Didn't update version of file, war2combat is still 4.3.3 since several more releases...
In versions en/ru lite/full/std.
You don't actually need it on XP for compatibility reasons, but now they're useful because we have windowed mode and stretching. I Always test everything on XP and 10, so yeah, it works fine
Yes, the main reason is window mode. Also some palette troubles happened in XP also. Nice to see you test it on XP also!
My main test comp in win7.
BTW, one of our testers still uses XP SP2, no way to update it to SP3 for some reasons. As i understand, need to rebuild ddraws with vstudio 2015 to use it on XP SP2, is that a good idea?
No, only what is written inside of ddraw.ini. Normally you don't have to change any settings, unless you're wanting to change something specific like the mouse speed or scaling.
I see, np, i'll try to understand that myself asking you. Looks like you understand that ddraw-gdi-dib-opengl-d3d things very well! I still continue looking into the source code and not understand what each command means and what effect it causes...
There are some config programs already available that can change the cnc-ddraw settings, but they're for other games and have game specific settings so we can't use them directly (We could modify them, but they need the .NET framework 2.0).
I see, i don't think we need to do something with that right now.
But for future i think that could be useful to make that module configurable.
Are there source codes for that framework 2.0 settings config utilities?
I'm about CNC ddraw most likely, i agree there's almost nothing to configure in arqit's ddraw.
war2 needs at least 60 FPS, but it's no problem to set it higher. I usually set it to the double of what the game needs to get less input lag.
I tried it with 1600x1200x32, used cubic.glsl shader as the most beatiful for me and with default 125 fps, and looks like it lagged on my core i5 processor. Then i decreased fps to 30 or w/e and lags disappeared. So, i think fps can be important.
For war2 we only need GDI, cause it's the fastest on low resolutions. OpenGL is only useful if you enable stretching cause it can apply shaders for better image quality. There are also shaders that can apply other effects without stretching (e.g. make the image brighter).
You mean a war2 resolution or screen one? Because i used opengl to scale war2 to 1600x1200x32. I didn't test cnc-GDI for such resolution. Should i?
That is currently not possible, it will switch to windowed mode but the window will be stretched and big... But it's a good idea, I have to think about a solution for this...
Yes, as i understand, there's only 1 current resolution for both fullscreen and windows mode. So, my idea is to set 1600x1200x32 (similar as default monitor in windows) to enjoy fast alt-tab between war2 and windows without switch videomode. And need another resolution for window mode.
You can do all that via shader= too. Each shader has a different effect.
gog's scaling looks blurry like this "shader=Shaders\cubic.glsl"
I see. I don't think that's important to make it "same as in GOG", just asked. So, i see they also should use some kind on shaders also.
Oh, are you sure you had 'fullscreen=true' set? That should always work with 0,0 on all renderers.
Hm, i've been sure yesterday when i checked. But now looks like everything is fine. resolution is auto: 0x0x0, fullscreen=true, windowed=false, boxing=false, shader=Shaders\cubic.glsl, renderer=opengl, and everything works fine!
So, i'll let you know if something become wrong.
The cnc-ddraw I linked here was a new test build, you have to switch the branch from "master" to "diablo_warcraft2" to see the new code.
Here is a direct link to the code of the new branch https://github.com/CnCNet/cnc-ddraw/archive/diablo_warcraft2.zip
Ah, i ddin't see that, thx!
I will do some testing. So this was the new test2 or cnc-ddraw? It only happens in windowed mode?
It was test2. That is a floating error, so he have no idea when is happened, but most likely in windowed mode. If you have no idea what is can be, then np.
I'll try to test it myself and give it to several more beta-testers. I hope they will quickly find bugs if they exist...
Also, an idea:
maybe would be good to write logs somewhere like ddraw.log or war2_ddraw.log, for debug purposes? Then people can send that reports to you, to let you look and check what happens on their side.