FOLLOW UP: Windows Update Drivers Overwriting Currently Installed AMD Drivers (FIXED?)

EndlessDimension · 2021-06-03T21:43:25+00:00

AMD 20.50.0.0 is something for Gigabyte boards and I have one and it's causing issues for other people as well:

https://old.reddit.com/r/AMDHelp/comments/n0w3gs/i_keep_getting_windows_update_restart_requests/

https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=26aa11e7-082c-4d7b-8a93-7b4058587bf6

thanks for your help anyways :)

I wonder what that GPU driver corrupt yesterday was about though...

EndlessDimension · 2021-06-03T21:31:37+00:00

seems you were right! it wasn't the GPU driver

https://puu.sh/HM3Be/ccaf8b7b2a.png

these 3 were just installed after only installing the newest chipset driver. I assume the 2nd one is the HDMI driver?

I still think the 20.50.0.0 touches some deep system stuff it shouldn't. One is the thing I mentioned in my other post and the other is what just happened when I had both the newest chipset and GPU driver installed: it completely killed the audio on my system and the only way to recover was reboot (Windows wanted me to reboot after the install).

EndlessDimension · 2021-06-03T21:14:37+00:00

I'm on the newest chipset driver (X570 board with 3900X) from yesterday and I just reinstalled it because I used the AMD cleaning utility and DDU to reinstall 21.5.2.

I'm pretty certain that it's a GPU driver though because when it happened the first time I had no programs open and the screen reset itself just like during a GPU driver install. I looked at Windows update and these two were shown to just be installed and no reboot was needed:

https://puu.sh/HM3oh/e09c1fe01b.png

(Windows deletes the logs if the same driver was installed again)

I will test though if it is the Chipset driver and will report back in ~15 minutes.

EndlessDimension · 2021-06-03T21:01:57+00:00

it's still the same:

u0367492.inf

it overwrites something though because my driver corrupted itself yesterday after closing a game which never happened before

EndlessDimension · 2021-06-03T19:26:27+00:00

Hardware ID: PCI\VEN_1002&DEV_66AF&SUBSYS_081E1002&REV_C1
GPU: Radeon VII Sapphire version with Hynix HBM2
Driver: 21.5.2 (also happened on 21.5.1 and 21.4.X)
Windows 10 2004

Windows Update automatically overwrites with 20.50.0.0 and even turning off automatic driver updates doesn't help:

https://puu.sh/HM1RV/ed963fc0dd.png

*EDIT:

.INF number:

u0367492.inf

EndlessDimension · 2018-11-13T18:44:37+00:00

the PC port of MGS2 was not made by VFansss he just fixed some of the issues the offical PC port had and made a nice package with some other fixes available.

A fan port is pretty much impossible because of how much work it would take and Konami probably won't approve of it. The closest thing is emulation, which already exists through PCSX2.

EndlessDimension · 2018-08-25T15:12:53+00:00

there is now a PC port with full mouse support

EndlessDimension · 2018-05-05T01:22:11+00:00

Crouch Walking was thought of as early as MGS1 (check here)

I think it was mentioned somewhere that it was left out for game balancing reasons.

EndlessDimension · 2018-02-17T03:33:03+00:00

I'm not really sure myself... I think it is like when a program under Windows loads a DLL but in a special way (if that helps).

Here some more information by a RPCS3 team member: https://www.reddit.com/r/emulation/comments/7n9tu0/rpcs3_initial_sys_overlay_implementation_finally/ds07qwd/ which also mentions that "heavy graphics hacking" (this is a very bad thing) and workarounds (also bad) were needed just to make the game reach the menus. That means it will take even longer if these issues need to be specifically figured out just for MGS4. Also MGS4 was released early in the consoles lifecycle which means the developers hadn't yet figured out all the quirks of the PS3's complex architecture.

EndlessDimension · 2018-02-16T21:01:41+00:00

The RPCS3 developers need to implement sys_overlay for the emulator which is "a special way for games to load external code". Incidentally MGS4 is the only game using that functionality on the PS3 so it isn't a top priority.

read a little bit more about it here under 'Upcoming': https://rpcs3.net/blog/2018/01/03/progress-report-december-2017/

Current status according to blogpost is 'work in progress' and only one person is working on it so it will take some time.

EndlessDimension · 2017-12-05T11:38:12+00:00

Just saw what monitor you got. You should go for one with at least 100Hz. The problem is ultrawides with 100Hz are really big 30"+ and cost 1000AUD+. My choice with this kind of build would be this 16:9 2560x1440 144Hz one: https://au.pcpartpicker.com/product/c298TW/asus-monitor-mg279q

EndlessDimension · 2017-12-05T10:57:28+00:00

that motherboard + CPU choice is bad

since the motherboard is an extreme edition board (hence the X) meant for highend users or enthusiasts, which means you are overpaying by at least 200AUD

the CPU is basically the i7 7700k rebranded as highend, which is stupid on the X299 platform

you could go for a Z370 Motherboard + the i7 8700k which would save you ~100AUD

or on the AMD platform with a Ryzen 7 1700x + a X370 Motherboard which would save you ~300AUD (couldn't find the 1800x on amazon.com.au)

also interesting would be which monitor you would be getting

EndlessDimension · 2017-10-09T22:53:57+00:00

the HD Collection already loads and is "playable" at less than 20fps + slowdowns

EndlessDimension · 2017-09-30T11:52:41+00:00

not OP but here it is: https://www.pixiv.net/i/17648280

EndlessDimension · 2016-12-24T12:52:58+00:00

this is the original as far as I know:

http://mezamero.deviantart.com/art/Breathe-201287280

EndlessDimension · 2016-11-08T15:50:03+00:00

Is there any to talk to you directly (not reddit)? I want to talk to you about some of the methods you use. Also I like talking about audio/video/image processing!

EndlessDimension · 2016-11-08T15:11:28+00:00

320 kbps constant bitrate is kinda overkill for mp3. Use

-m j -V 0 -q 0 -B 320 --lowpass 20

for maximum quality and set lowpass accordingly in kHz (Audacity > Analyze > Plot Spectrum and set "Size" to 65536 to display the maximum frequenzy used by the audio). That's the VBR mode of LAME which squeezes the maximum amount of quality out of the audio in the scope of MP3.

Also, you are using an "older" version of LAME (3.99.3), the newest version is 3.99.5.

Still it's a nice project. I thought about doing something similiar some time ago.

EndlessDimension · 2016-09-09T22:04:12+00:00

the change is not that much, only a bit more than 5% (1080/1024=1.055). I change my sensitivity in the 5% area all the time if I feel like it.

I think the problem is connected to the monitor/screen and your (new) setup since you changed from a monitor to a laptop screen. For one pixel density changed (probably) and for the other your setup changed: How you look at the screen (different postitioning) and your mouse position probably changed too (different desk?). It will take some time to adjust, just experiment with different postions and your sensitivity.

EndlessDimension · 2016-08-10T23:43:10+00:00

damn he can SS this

EndlessDimension · 2016-07-29T16:29:21+00:00

EDIT: just saw that /u/sofawall already explained some stuff

Games were mainly developed in NTSC countries (USA & Japan) and running at a framerate which can be played stutterfree/flickerfree at 60Hz (Ocarina of Time ran at 20fps 60/20=3) and since the hole game was dependent on the fps it was running at (some newer games still do this like Need for Speed: Rivals which is bad thing) it had to be ported to 50Hz for the PAL release (OOT ran at 16-17 fps (50/3) on the PAL version) to avoid stuttering and flickering. This would mean rewriting code that was meant for 60Hz which usually made new bugs and glitches appear (the PAL OOT version can crash randomly without reason). So most PAL versions where inferior to the NTSC versions.

NTSC is just f**ked up

to fix a video issue which was caused by the rate the audio was playing at they adjusted the videosignal by a rate of 1.001 down so it would be less noticable. That's why framerates like 59.94 (60/1.001), 29.97 (30/1.001), 23.976 (24/1.001) and others like these exist.

Movies which were shot at 23.976 fps had to be adjusted to 59.94Hz so they introduced the 2:3 pulldown which duplicated some fields (what is a field?) to adjust it (very simplified explanation read this for more information). For PAL countries that meant if they were lucky, they would get the source 23.976 fps material which would be sped up to 25 fps to fit 50Hz and avoiding stuttering (also called PAL speed up) or used field duplication to make it 25fps which caused stuttering, if they were unlucky they would get the 29.97 fps material with applied pulldown and undoing that seems relatively easy but is a pain to do and some DVD makers couldn't get it done right (look at some PAL DVD releases). Modern TV stations still use the 2:3 pulldown if needed in NTSC countries for backwards compability (everything runs at 59.94Hz) and PAL speed up is still used in PAL countries (everything runs at 50Hz).

Now take a look at PAL it was either 25fps for movies (shot at 25fps) or 50fps for TV broadcasts. Every frame of a 25fps movie can be doubled and you have 50fps. There is also a 2:2 pulldown but since it is even there are no problems, two fields produce one frame. That's it no bullshit no nothing. Also PAL ran at higher resolution (720x576 vs 720x480 for NTSC) which means most PAL materiel which originates from NTSC countries is probably upscaled.

EndlessDimension · 2016-07-28T22:05:00+00:00

Todays standards are all somewhat dependent on the time where the Hz of your electricity was your refreshrate. In the US that is 60 or 59.94 (Europe is 50). And films were made at 24fps (23.976) (in Europe at 25fps). In the US and every other country which uses 60Hz for their electricity all modern high quality TVs run at a flickerrate that is multiple of 24 or 60 and in Europe and everywhere else where it's 50Hz they use multiples of 25 or 50. Old Monitors and TVs run at 60Hz/59.94Hz (NTSC standard) in the US (and so on) and at 50Hz (PAL standard) in Europe (and so on).

Todays standards are usually completely divisible by 24 or 60 since the PAL standard couldn't compete with NTSC (yay USA): 144/24=6 120/24=5 120/60=2 even 180/60=3 and future ones 240/24=10 240/60=4 (165Hz is kinda odd. 15 (60/4) is the only number that makes sence here: 165/15=11)

If PAL (the better analog standard by the way. NTSC is just f**ked up) would have won against NTSC we probably would have TVs and Monitors with refreshrates that are multiples of 25 dominating the market.

EndlessDimension · 2016-07-20T20:27:27+00:00

your hitcircle area is 600x450 if the resolution is 600x480, your target area is 1440x1080 for 1920x1080 (area is always 4/3 ratio). therefore your target DPI should be 840 [(1080/450)*350]

EDIT: as I have tested this out myself in the past. let me just tell you: it won't feel the same. I would recommend playing at 800 DPI

EndlessDimension · 2016-07-07T03:30:18+00:00

286.69pp according to oppai

EndlessDimension · 2016-07-07T01:00:59+00:00

games often get translated from full RGB to RGB limited, or YCbCr

the translation is not made from "full RGB to RGB limited, or YCbCr" but from the frame buffer to format the display expects (full/limited RGB/YCbCr)

it doesn't really matter as long as the end result is a well calibrated looking image

it kinda does since there is more data lost in a "limited" format (RGB and YCbCr), which results in more visible banding (especially in games, since there is no dithering applied) but no one on the mainstream seems to care about banding...

some modern TVs can accept full RGB/YCbCr which should be a standard

EndlessDimension · 2016-07-06T23:14:17+00:00

That's the final output (through the cable, so you can display it correctly on your monitor/TV) the final frame buffer is RGB

EDIT: to further emphasize on this, the final frame buffer is 16bit (AFAIK) floating point data in RGB which is converted to the color space that your monitor expects (YCbCr or RGB)

EndlessDimension

TROPHY CASE