Загрузка видео...

Не удалось загрузить видео

На главную

Monster Hunter Wilds big performance patch is out on PC. I spoke with the user who originally discovered the DLC bug and they confirmed that it seems to be fixed. More improvements I noticed from some quick testing (continued): • Better 1% lows for smoother gameplay with less hitching...

294,509 просмотров • 5 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

In my previous post about the #Nioh3 demo, I mentioned that when the game isn’t consistently holding 60 FPS or 120 FPS, several issues can show up. Here’s a clearer breakdown of what's going on. The main reason is that the game speed and physics are tied to the frame rate. When you enable the 120 FPS cap, the engine start overreacting and pushes CPU usage very high, even if the game is still running at around 60 FPS (as shown in the first example). In the second clip, you can see the uneven, jittery camera movement I mentioned before. Notice how much smoother 60 FPS and 120 FPS look compared to the unlocked side. Also, camera movement at 60 FPS is slightly faster than at 120 FPS. In the third clip, player movement is slower when the frame rate is unlocked. This doesn’t happen all the time, but it shows up often enough to be noticeable. Because of how the Katana Engine behaves, the game is clearly designed around 60 FPS. Running at 120 FPS is possible, but it’s only recommended if your system can maintain that target almost all the time, which isn’t easy to achieve. There’s also an alternative workaround where you select the 60 (locked) option and enable Frame Generation (DLSS or FSR 3), as shown in the last clip. The downside is that DLSS Frame Generation tends to show the same stuttery look as when the frame rate isn’t holding a fixed target, likely due to Reflex keeping the frame rate slightly below target. FSR Frame Generation, on the other hand, looks much smoother and works better here.

BenchmarKing

17,820 просмотров • 5 месяцев назад

** MEGA Parodius Scaling Effects Part 1 ** One of the big challenges with the Parodius Megadrive port is Stage 8's boss - The puffer-fish *Pooyan* with his full screen scaling effect. The goal is to be very close to the arcade (with extras on top ) so I thought lets tackle it head on to see how close we can get. I was also keen to jump into another scaling code rabit hole haha. Pyron pulled out all the stops and got me the source frames and reworked the BG tiles for this test - a big thankyou to him , Vector Orbitex is busy working on Stage 2 tracks so the team is working hard all round on this port. The MD has no sprite / background GFX scaling hardware , however the VDPs Vertical scroll can be updated per scanline to help vertical scaling on backgrounds, but there is a cpu cost to manage all the interupts so thats not free either. With the Horizontal scaling there is no help at all , apart from a semi-friendly packed pixel format for the cpu to work with, its not quite chunky format but better than planar format still for scaling. So its falls back to the 68k CPU to do all of the horizontal expansion which is the largest cpu cost. Basically drawing strips of either 1x, 2x, 3x or 4x wide columns at speed. So we are one week into this Boss's routine and you can see from the below video the horizontal scaling is implented ( vertical will be in the next update ) . We are scaling from 1x to 4x in the video below in 74 steps for testing . The column distributions are always a bit painfull to do - thankfully they are all worked out now. This is the third scaler I have built and the goal was with this one to make it really flexible for use in other projects also, sometimes when you optimise something to the last degree all the flexibility gets taken out of it. Currenty scaling at 12-25 FPS update here, I had some rules against some optimisations which I would use and some I wouldn't , thankfully we are a bit ahead of the Arcades animation frame rate here still and I may yet find optimisations that fit within the scope. We have vertical scaling and sprite spikes to add yet so Im hoping i can find a few more optimisations to offset things when they are implemented also. In a scale frame update we are processing close to 42000 pixels in ram before using DMA to send to VRAM . Using a 41x16 (656 tile scale buffer) - single buffered for now due to its size in VRAM. So thats nearly 21k in tiles ! I had to re-organise ram a bit to support a buffer of that size for the stage. The scaling function is written in 68k assembly , with a little C code handling the Vertical interupt code ( so the game logic can actually run & DMA updates etc ) . The DMA routines are in assembly also and customised for large chunk size ( big blocks of tiles ) which suits the scaler. I had some race conditions to sort out where the cpu was faster than DMA (sending tiles from RAM to VRAM ) and in some cases where it wasn't so it had to be balanced. We may be able to add more detail into the top and bottom of the background yet but its low priority for now until all the other bits are in !! #SGDK #SegaMegadrive #Genesis #Parodius

Shannon Birt

25,545 просмотров • 5 месяцев назад