Notice to Windows 10 users

[Jason Petho]

Good day

Although we believe that the Campaign Series: Middle East works on all supported systems, there are a few reports of some game features causing issues on certain Windows 10 setups.

We intend to investigate any Windows 10 issues more fully in the not too distant future. In the meantime, we regret any inconvenience.

Please consider this in case you are thinking of upgrading to Windows 10.

Thank you for your patience and understanding.

Jason Petho

[harry_vdk]

Jason,

If needed I can run some test on my secondary pc.

Its a laptop: Win 10 Enterprise b10240. i5-2540M 2.60GHz, 16GB ram, AMD FirePro M5950,

[Jason Petho]

That is excellent to know, thank you, harry_vdk!!

[Crossroads]

ORIGINAL: Jason Petho

Good day

Although we believe that the Campaign Series: Middle East works on all supported systems, there are a few reports of some game features causing issues on certain Windows 10 setups.

We intend to investigate any Windows 10 issues more fully in the not too distant future. In the meantime, we regret any inconvenience.

Please consider this in case you are thinking of upgrading to Windows 10.

Thank you for your patience and understanding.

Jason Petho

The thing with Windows 10 seems to be that there's still areas that seem to be in a state of flux. It is at times very difficult to us to pinpoint exactly what's going on, is it the game or is it the O/S. For instance while investigating an issue where selecting a unit was causing difficulties, we found out several reports that in fact Mouse use itself was causing problems to several W10 users.

I converted my desktop to W10, and in general I am really liking what I am seeing with W10. There is some weird issues at times, for instance I am having at the moment issues for playback when using Chrome, but no issues with Edge browser. Might have to do that Sound set up refuses to open at times from Control Panel.

I guess what I am saying is that W10 has all the makings of a great operating system, but there seems to be some teething issues there as well. Oh, there's definitively still bugs waiting to be found from CS:ME as well, but hunting them down, identifying one from the other, even replicating confirmed bugs in our test environment seems to be more challenging than what it used to be with W7 and W8.

We have a W10 desktop and W10 laptop in our test setup, and I'll be darned if they behave in a similar manner (they don't).

Indeed: Thank you for your patience and understanding.

[zakblood]

i'm always here for testing if needed, don't play many games but test most days alpha's and beta's when and if needed, run 5+ pc's of different types, can install most O/s on them in under a hour as all are imaged.

at the moment im a windows 10 64bit pro user, on build 1511, but also have Windows 10 Insider Preview builds as well.

dual core, core duo E6850@ 3GHz with 6gb

dual core Core 2 Duo E8400 Wolfdale 3.0GHz 3gb of ram

i5 3230m-3.0ghz 4gb of ram onboard vga chip

i7 2700k cpu with 16gb of ram

i7 3960X cpu with 32gb of ram

Win 10 1920x1080 or less, or even more on one monitor.

[Crossroads]

Thanks Zak! At times we are quite struggling to replicate a reported issue, so more the merrier [:)]

[harry_vdk]

After reading the info from Mouse use itself was causing problems to several W10 users..

I was question myself.
If you compare CSME with the older CS titles. Are there W10 players with both games.
- Having the same problems.
- Having partial the same problems.
- Having non of the same problems.
Perhaps can this give some clue's.

I use my W10 laptop primary for testing of my daytime work and some private actions but not for gaming. And its running without problems but I prefer the W7 on mine main pc.

[berto]

I tried kludging around these Win 10 issues, but abandoned the effort. It was like attempting to solve Rubik's Cube. An endless sequence of fix one thing, break another. Worse still, the possibility of breaking the game for Win 7,8,XP users for whom the game has, and still does, run fine.

The Win 10 mouse & keyboard issues are real -- for some users, but not all. It seems to be hit or miss, depending on the system, the peripherals, the setup.

One purpose of an operating system is to deal with low-level program-to-peripheral interfacing. Normal application coders write to a standard high-level API, which is just supposed to work. Normal application coders should not have to deal with low-level hardware details, much less account for the 1,000s of different mice & keyboards available for PCs across the years.

It's an operating system issue, and/or mouse & keyboard device driver issues. It's up to Microsoft and/or the mouse & keyboard vendors to fix. Either universally, by default, or by way of special Compatibility modes.

ORIGINAL: Jason Petho

Thank you for your patience and understanding.

[harry_vdk]

Perhaps you can consider a special build of the exe/dll for W10 and a regular build of the exe/dll for the other windows version.

And let the setup/installer decide with version is needed.

Are there difference between VS2008 and a later version of Visual Studio?

[zakblood]

yes, different dll




which some games needing a certain one, while others needing a different one, as my screen shot shows, test enough games and the list gets rather large, shame 2015 doesn't have or use all the same ones as all the others, then again the x86 is different from the x64 bit one as well so even on a 64bit O/S you still need to load the 32bit version x86 for a 32bit game to work, daft really now days why one can't do them all either

[berto]

ORIGINAL: harry_vdk

Perhaps you can consider a special build of the exe/dll for W10 and a regular build of the exe/dll for the other windows version.

And let the setup/installer decide with version is needed...

Instead, I considered having the game engine determine the OS on the fly, set a boolean flag internally, then call the appropriate OS-specific functions as needed.

But figuring out the kludges was too difficult, and one kludge was leading to another.

Kludging should not be necessary! Game coders shouldn't have to play whack-a-mole with the OS & drivers. The OS/peripheral drivers should simply work, as they always have. Preserve backward compatibility!

No, better to wait this out. See if some future Win 10 auto-update (they are all forced automatic now!) resolves these issues. Or wait and see if there is a sure-fire way to fix peripheral drivers, if that is the actual cause. (Some users have reported success purchasing new keyboard and/or mouse.)

If you have a new Win 10 system, it all either works for you, or it doesn't. If it doesn't, please be patient. We will investigate this further in the coming months. (We will not delay the imminent ME 1.01 update due to this issue.)

If you have an older systems with an option to upgrade to Win 10 -- and if you value playing the Campaign Series (old & new) -- consider not exercising the option. For the upgrade might break the game(s)!

[zakblood]

windows free upgrade is only free until July 29th 2016, after this date to upgrade you will need to buy it, if you register for it now but don't install it, then you can install it at any time for free

Code: Select all

http://windows.microsoft.com/en-us/windows-10/upgrade-to-windows-10-faq

[berto]

ORIGINAL: berto

If you have a new Win 10 system, it all either works for you, or it doesn't. If it doesn't, please be patient. We will investigate this further in the coming months.

Although I have a Win 10 test system available (my wife's laptop, upgraded to Win 10 last weekend, for purposes of testing CS), I can't debug coding issues on it directly. After I build new versions on my primary Win 7 dev system, I am forced to copy over Release (not Debug) versions of the game to the Win 10 system -- added awkwardness and delay.

I have plans to purchase a new Win 10 desktop as my new primary dev system in the near future. I hope and pray everything will work properly on that system. (Could be. It might be that these mouse & keyboard and other issues don't affect default Win 10 installs, rather, a fraction of Win 10 upgrades only. You would think that PC sellers would ensure that everything on their brand new Win 10 systems is WAD.) If it doesn't, I will be highly motivated to seek a fix, won't I? [;)]

[barkhorn45]

ORIGINAL: berto

ORIGINAL: harry_vdk

Perhaps you can consider a special build of the exe/dll for W10 and a regular build of the exe/dll for the other windows version.

And let the setup/installer decide with version is needed...

Instead, I considered having the game engine determine the OS on the fly, set a boolean flag internally, then call the appropriate OS-specific functions as needed.

But figuring out the kludges was too difficult, and one kludge was leading to another.

Kludging should not be necessary! Game coders shouldn't have to play whack-a-mole with the OS & drivers. The OS/peripheral drivers should simply work, as they always have. Preserve backward compatibility!

No, better to wait this out. See if some future Win 10 auto-update (they are all forced automatic now!) resolves these issues. Or wait and see if there is a sure-fire way to fix peripheral drivers, if that is the actual cause. (Some users have reported success purchasing new keyboard and/or mouse.)

If you have a new Win 10 system, it all either works for you, or it doesn't. If it doesn't, please be patient. We will investigate this further in the coming months. (We will not delay the imminent ME 1.01 update due to this issue.)

If you have an older systems with an option to upgrade to Win 10 -- and if you value playing the Campaign Series (old & new) -- consider not exercising the option. For the upgrade might break the game(s)!

Yes i found out about the auto-update feature/problem when it updated my vid card driver and media player would not run.
Tech support informed me that because people were having problems because they did not update regularly
microsoft decided to releave us of that burden.Thx big brother,you can avoid it by rescheduling but eventually it will insall.
Another problem is that when it installed i checked restore and it had not created a restore point at the time of install.

[Three63]

I'm going to buy a new Desktop kinda soon so I need to know, do CS games, JT Battleground Nap./Civil War and most Matrix/AGEOD games coming out work ok with Windows 8 (or 8.1, are they pretty much the same)? Will older Matrix PC games from the 2000's be ok on that OP? I'll avoid Windows 10, cause if there is a chance of my games not playing on it it's not worth me buying.

[Crossroads]

The reason we made this thread a good two years ago was we were - at times - seeing some strangest symptoms we just couldn't figure out, for instance the mouse not working with this game with one or two players, and then finding out the freshly out W10 was the culprit. Teething issues, we suspected.

Now, two years later, its become quite popular, with latest Steam Survey reporting over 50% of the gamers have moved to W10 64bit. W7 64bit is a solid #2, at 35%, and W8.1 a distant third at 6%. So most W8.x have moved into W10 it seems.

I've really grown into W10, have the latest Creator's Edition update installed, and would not go back. Unfortunately, I only have the JTCS series of older games on my disk.

Here's the Matrix W10 Compatibility List, see if it helps.

Also, perhaps consider posting at the various forums at The Blitz, they might have the latest for you.

[Three63]

So it works fine? It listed Campaign Series as bieng ok. I'm not as worried about my other games as I'm worried that CS ME and the new ones coming out for CS will not work. So your basically saying the new Windows 10 updates got rid of the issues?? I guess I have my old Desktop in case all fails.

[Crossroads]

Yes, I have played CSME on W10 64bit since late 2015. Knocking on wood, but really liking the W10 Creator's Edition [:)]

Edit: You asked specifically about CSME 2.0 and future games and W10. Going forward we are making a conscious effort to support W10 as the default platform everyone's using. For one, the programming environment has been updated to MS Visual C++ 2015 (W10), from MS Visual C++ 2007 (W7). W10 is the way forward, yes.

[Oberst_Klink]

The 2 important links within the forum to solve the Windows 10 display/Direct Draw and scaling issues:

fb.asp?m=4425331

fb.asp?m=4424891

Klink, Oberst