Results 1 to 28 of 28

Thread: Redux & W7...

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Default Re: Redux & W7...

    Hello Tomas, welcome to this forum and the Redux-area…

    From what you are telling me in your post, I guess it is your (legacy?) Nvidia-drivers that are fussing with MTW/Redux. If they don’t get along - and you have no other drivers to try (to get better performance) - I simply suggest that you stick to using that old PC you are talking about. At least while playing Redux/MTW. For some reasons, and this is very common, some 10 year old hardware, typically/often outperforms newer hardware when it comes to MTW. It’s a well established truth since many years. In my experience, the best OS I ever saw for MTW was/is Win2000pro and the drivers made for that. W7 can be very good, assuming we have hardware that gets along with MTW, in the first place (typically this means ATI/AMD cards, among other things)…

    The solution (as I understand it) is that you get an ATI/AMD GFX-card for your primary rig, something like HD 58xx or HD 68xx-cards. One of those cards should do just fine on W7-drivers (I got have twin ATI HD5830 cards, although “crossfire-mode” will basically crash MTW). If that is somehow impossible, then get some 2nd hand/used GFX-cards – and make a point of it being ATI/AMD cards (due to drivers and MTW). The last possibility here, as I see it, is that you keep that old PC and have it as a dedicated machine to MTW and perhaps other old games that you like, and keep it around for that very purpose. A “legacy-rig” if you will… As for the battles and lag on that rig… In MTW options, set sound quality to “medium” and the lag in battles should disappear, or at least get much less frequent…

    Other then that… Feel free to post up your Redux-experiences over at the main thread, or if there is something else that interest you in the other threads, by all means post there...

    - A
    Last edited by Axalon; 01-14-2014 at 23:57. Reason: English!

  2. #2

    Default Re: Redux & W7...

    Quote Originally Posted by Axalon View Post
    A note for all people using gaming/high-performance monitors such as the BenQ XT2411T (or similar)...

    I noticed that using high refreshment-rates like 120-144Hz can turn out problematic on MTW-resolutions as it is then drastically reduced (to 1024x768) since the game-engine can't seem to properly cope with it - both for Redux and raw MTW. It seems like 100Hz is the max before the game seriously freaks out like that. For higher resolutions (such as 1280x1024) use refreshment rates below 100Hz, like 75Hz should be safe. Alternatively, change the "True color 32bit" display-settings to "High color 16bit" and it seems MTW/Redux then becomes far more cooperative/agreeable to such newer hardware and its drivers.
    To clarify this stuff somewhat...

    Setting color-depth to 16bit will not increase the tolerance-levels of high refresh-rates (like 100-144hz). Max will res still be 1024x764 regardless of anything - and that res will actually look pretty good on Redux, especially on 120hz (full screen on a Benq 2411T, latest W7-drivers). The highest refreshment-rate I managed to test is/was 144hz, and it will work fine, but not look as good as 120hz (and full screen, which was not available for 144hz) do, to me. Ergo, setting color-depth to "High Color 16bit" somehow strikes me as pointless in this context as it will not achieve anything other then just robbing you of possible color-depth.

    Also, the Sepheus-fix will not help much in this given context, as it will not change any of the above outlined circumstances (as far as I can tell). The only thing the S-Fix does to RXB1005 is seemingly forcing the use of a low res-campmap texture, and limiting the available ram to 254 Mb (from the otherwise possible max of 3837 Mb. If I got the numbers right).

    - A
    Last edited by Axalon; 08-18-2014 at 20:38. Reason: details

  3. #3

    Default Re: Redux & W7...

    Everything is working great for me now with the ddraw, but the province names don't show up on the campaign map.

  4. #4

    Default Re: Redux & W7...

    Hi Jingo7,

    I did not include the province-names in the low-res campmap-texture as I thought it looked poorly, and so I decided to have a blank map instead as (I thought) that looked much better in low res... I guess it is the price you and others will have too pay for using the S-fix on Redux anyway - despite it is not necessary somehow for it in order to function. Redux is and always was intended to use the high-res texture (and this of course has all names as usual) - using the S-fix prevents Redux from using that higher texture altogether. As a result you get the RX low-res texture (and no names)...

    - A

  5. #5

    Default Re: Redux & W7...

    What do you mean? Without the S-fix my game crashed constantly, res was stuck on very tiny. Are you saying it is not nescessary? I think I have misunderstood you.

    Anyway, the game is fantastic, and very challenging. The province names is a minor quibble.

  6. #6

    Default Re: Redux & W7...

    Strange... It may be a matter of specific hardware and drivers somehow... My experience on W7pro 64bit, this on all the hardware available to me, is rather clear - Redux does not need any S-Fix to function just fine (in fact it functions better without it, as the map then looks as intended). I can have 1280x1024 or 1024x768 (and others) without problems or fixes, always could with Redux...


    Quote Originally Posted by jingo7 View Post
    Anyway, the game is fantastic, and very challenging. The province names is a minor quibble.
    Thanks...

    - A

  7. #7

    Default Re: Redux & W7...

    Courtesy of Frunk (over at the TWC), I received word that a W7-update - KB3086255 - may cause problems and issues for MTW, and thus Redux too... His original post (from September 11, 2015)...

    Quote Originally Posted by Frunk
    The disc versions of Med2, Rome1, Med1 and Shogun1, that is.

    When Windows 10 came out, many of us here quickly discovered that while we can successfully install Med2, Rome1, Med1 and Shogun1 on the new operating system, these games will not run. Now, with Windows update KB3086255 being rolled out this week for Windows 7 and Windows 8 users, the same problem will now affect even more people.

    The problem is that a Windows XP-era third-party driver called secdrv.sys has been disabled in Windows 10 and now also 7 and 8. It is required to run SafeDisc, an outdated and mostly ineffectual form of copyright protection. SafeDisc protection is built into hundreds of older games and is meant to check whether or not the disc you are trying to run your game from is legitimate, or pirated. With secdrv.sys disabled, SafeDisc cannot run, and therefore neither will the game as this process must be completed. The games will not run via their .exe files, shortcuts, Autorun or the Launcher - they will not run at all.

    This is the only thing stopping the four oldest Total War games from running on W10, and the issue has been present since W10's public release. There is no legitimate fix that resolves both the security vulnerabilities and the lack of SafeDisc functionality.

    This week W7 and W8 users will likely be asked to install Windows update KB3086255, which turns off secdrv.sys for the same reason.

    Quote Originally Posted by Microsoft
    "In addition to the changes that are listed for the vulnerabilities that are described in Microsoft Security Bulletin MS15-097, this security bulletin addresses a defense-in-depth update for the secdrv.sys driver, a third-party driver. The update turns off the service for the secdrv.sys driver. This may affect the ability to run some older games.

    To learn more about the vulnerabilities, see Microsoft Security Bulletin MS15-097."

    A workaround using registry editing exists at that link, which can turn secdrv.sys back on, presumably resolving the issue, but Microsoft recommends that it be turned off again when you are done with it, which would surely be very impractical for users who run the games every day. Of course, one could theoretically turn it on and leave it on, but this would leave your PC vulnerable to infection, and would be the same as not installing the KB3086255 update at all, which certainly is not advisable. Furthermore, I am uncertain whether this method would be applicable to W10, or just to W7 and W8.

    Medieval 2 escapes the issue somewhat, as it appears that while SafeDisc exists in medieval2.exe, it does not exist in the Kingdoms expansion's kingdoms.exe, which of course runs mods. GurneyMan, who brought the KB3086255 update to my attention, can confirm that Kingdoms runs on Windows 7, whilst I have been playing and modding Kingdoms on Windows 10 for the past month without any issue. The only thing that we lose, therefore, is the ability to play the original Grand Campaign, but in fact it can be played in the form of Gignatus' Bare Geomod Kingdoms, which is the Grand Campaign in the form of a mod folder (used as a base for modding), so it uses the kingdoms.exe.

    Microsoft has done its due diligence by fixing the security issue, thus the onus must now fall back onto game developers to restore functionality to old games, in the form of the patch which removes the need for the crude SafeDisc check to be completed. Would Creative Assembly, for example, ever do this? Or would they be quite happy to take no action and force users to either compromise the safety of their systems, or abandoned the old Total War titles in favour of new ones? Only time will tell, and I'm considering starting a petition, should this prove to be as concerning to people as it is to me.
    - A

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Single Sign On provided by vBSSO