Dixel

You're fixed on @D.Draker's native tongue? Good choice, French is marvellous.

"Russian Businesses Can Now Legally Steal Intellectual Property from ‘Unfriendly Countries’" "As of Monday, March 7, 2022, the Russian government has legalised intellectual property (IP) theft. With this move, businesses in Russia can now violate IP rights, as they no longer need to compensate patent holders from “unfriendly countries.” The list of “unfriendly countries” includes the United States, Canada, Australia, Switzerland, Norway, Iceland, the United Kingdom, Japan, South Korea, New Zealand, Singapore, Taiwan and all 27 European Union (EU) member countries." That includes software. https://ipwatchdog.com/2022/03/16/russian-businesses-can-now-legally-steal-intellectual-property-unfriendly-countries/id=147528/

Judging by the amount of typos in the OP's post, I think it's a typo. It's 1030. Also doesn't work for me.

I agree with this guy, proven by the decades with my Keppler Titan and many games: "why nvidia removed CSAA? I thought was great with much lower performance overhead than MSAA" link

"Nooope! MFAA is MSAA where the samples coordinates change each frame. Each frame is independent. MFAA is implemented entirely at the driver level. TXAA uses previous frames as additional sampling points, and because of this it must be implemented by the game engine (in order to correctly retain previous buffers to pull samples from). MFAA at high (e.g. 60FPS) framerates will appear visually similar to higher MSAA levels* due to the human eye performing the temporal interpolation, similar to how interlacing worked in the CRT era. *e.g. for a two-frame sequence of MFAA, 2x CSAA will resemble 4x MSAA, 4x MFAA will resemble 8x MSAA. By using a longer sequence (e.g. 4 different coverage patterns) a greater improvement can be achieved, but will not be as effective without a higher refresh rate (see: MUSE sampling's issues at 60Hz).!" Source: https://hardforum.com/threads/csaa-removed-in-900-series-why.1840841/

No, it's not. Here's a MonoBleedingEdge (Engine version from 2019) log file for you from: OS-Version: 6.1.0 (win 7). Renderer: NVIDIA GeForce GTX 1070 (ID=0x1b81) GTX 1070 supports all the way up tp 12_1. Yet the log for Windows 7 says: "Forcing GfxDevice: Direct3D 11 GfxDevice: creating device client; threaded=1 d3d11: QueryInterface(IDXGIFactory5) failed (80004002). Direct3D: Version: Direct3D 11.0 [level 11.0]" Source: https://steamcommunity.com/app/251570/discussions/1/2646361461399067327/ It's from 2020! Eight years after the alleged 11.1 update KB came out.

My developer friend on github said they usually send an official letter demanding to remove the content in question, so not likely the case.

Nothing weird, I always suspected win32 stood behind all Kernel releases to begin with, it's just my personal opinion after looking at the code. Not seeking an argument over it.

It can't be classified as an "attack" in either of the cases, Microsoft has the right to defend what's theirs. Closed source Kernel modifications aren't allowed in the US,

You confuse hardware level with software level. "11_1 feature level" is a hardware level, it can't be "implemented" in just "soft" mode. Here you can educate yourself regarding the topic. Microsoft article with precise and simple explanations. https://learn.microsoft.com/en-us/windows/win32/direct3d12/hardware-feature-levels

From this first sentence it's clear as day that you implied that Microsoft actually did bring "D3D11.1 API to Win 7" And no matter how many games I tried to run on Win 7, even after the aforementioned update applied, they all fall back to just 11.0. So, D3D11.1 on Win 7 is just a stub, it's not "API" like you wrote. What it does, it simply tells a game, go on, run, it runs, but with 11.0 since the 11.1 features are absent. One would need to rewrite Win 7 to actually add the real D3D 11,1. That's what D.Draker tried to explain to you. As of now, Vista and Win 7 have the same 11.0. Is it more clear now?

Source, please.

What if you disable "safe" downloading or whatever they call it in Firefox?

Overall agree, but 900 series lack CSAA, which is a must have for old games.

Long pause before the posting is done came back.

Try portable.

Yes, the cutting off point from my tests for Win 7 and Vista is Chrome 125.0.6422.68, probably @win32will shed some light on the future of the Kernel, then.

Wow! Thanks for the feedback, those South Koreans clearly made a false advertising. So non-working on older OS, then.

Thanks for the feedback, I tried Catsxp 125.4.5.4, had no errors observed,

is doomed to be a troublemaker due to the heightened "security" measures against modded drivers and older games copy protections,

It doesn't let me to download. https://web.archive.org/web/20240727151625/https://github.com/i486/VxKex/releases/tag/Version1.1.1.1375

Agree! Only good PR for MSFN.

Compare with what? What if the user is new, and doesn't have any of these from before? Since the original repo is gone, as you wrote yourself.

You asked about Securom, specifically, Windows 8 has known troubles with Securom drivers, it treats them as exploits, hence the fact I suggested Vista.

All fakes, like the member above wrote. I'd also keep a close eye on this user @lll888. Before posting his fakes, he accused MSFN of being "almost dead" and hosting non-working projects. Here's my answer. https://msfn.org/board/topic/186324-disable-system-restore/?do=findComment&comment=1269459 https://msfn.org/board/topic/186324-disable-system-restore/?do=findComment&comment=1269432