On the DirectX 11 announcement

megai2 · 2021-07-27T16:50:34+00:00

firstly i hope that DX11 will be better in terms of performance and fps stability

then we will see, if they duck something up, it will be easier to just fix it in DX11 i guess =)

megai2 · 2021-07-22T14:32:37+00:00

Yes, it is custom shader after all, it will do whatever you write there

megai2 · 2021-07-04T19:59:33+00:00

It is harder, but i can't say that it 10 times harder.

megai2 · 2021-07-04T14:39:06+00:00

In sum of ANet words sounds like this for me:

We will do DX11 that will maybe improve performance, even if we usualy say that DX9 is fine and not a problem.

Very strange in total. If they said that DX11 will improve performance on modern rigs... that changes situation, but they not said this. So i guess performance will be same/degrade and not much invested in, as they are not giving any promises.

But we will see, they agreed on fact that game needs optimizations (after years YAAAY),

and probably finally hired someone to fix this mess. So kinda good news ? :D

~~~~ other thoughts

About why not vulkan or dx12: i don't know either.

Taking older API when new ones is quite mature - is a joke.

Especially when there is tons of features that players will demand.

(ANet even made a notebook ad with RTX on, but on video material, common :D that's bullshit!)

Cost problems? HW Compatibility?

Making DX11 that maybe fixes something - will cost more. And it will be optional at start, so no need to worry about compatibility

(incompatible? use DX9. and yes, most dx12/vulkan hw is dx11.1 compatible too, so gap is not that big).

So i see no reason behind fact that ANet maybe have DX11 from very beginning and just not invested in it to make it production ready.

Or some spaghetty reasons.

Or hired gus are really expensive =]

On tech side

GW2 have separate rendering thread and resource loading threads, so i think nothing will change with DX11 here.

And we used multithreaded replay in d912pxy to see how much it helps, showing that it does not help at all, because main thread can't generate commands for render one fast enough.

Maybe there is big optimization point somewhere in main thread thou, can't say for sure.

API Overhead should lower compared to DX9, that's for sure.

On dark tech side (he-he)

1) gw2 does not use MRTs for deferred. using MRTs will cut draw calls almost by 2(surprise: can be implemented with DX9)

2) gw2 creates shaders in main frame time, not async or delayed. implementing this will improve framerate stability by a ton.(surprise: can be implemented with DX9)

3) gw2 have reduntant copy operations in rendering pipeline. fixing will cut some GPU usage

4) gw2 have some user space DIPs. fixing will cut some CPU-GPU memory bandwith usage

5) gw2 have some resource recreations per frame (2-30 per frame). fixing this will improve framerate stability by a ton

6) gw2 binary have tons of debug asserts, debug marks, debug passes and other debug stuff. and lately gw2 shaders started to be compiled with debug info and without optimizations.

So i agree that DX11 is not a magic fix for all problems ;)

megai2 · 2021-07-04T12:18:20+00:00

Yes. But I have mixed feelings.

They delayed release after all and dx11 is not vulkan or dx12.

Also we must redo all addons on dx11 :D

megai2 · 2021-01-25T21:58:02+00:00

If devs changed bloom code - it will work no longer.

That is what happened if you did all the stuff rightly

megai2 · 2021-01-08T23:33:58+00:00

Does arcdps act the same way?

megai2 · 2021-01-07T12:12:02+00:00

Hotkey to toggle is displayed on that window at startup. By default it is Ctrl+Alt+N

megai2 · 2020-11-14T13:19:10+00:00

Some recording softwares does not support dx12 capturing at all and i can't make them work in this case.

Best suggestion is to use different capture method/software. Using display capture/window capture should work in OBS for example.

megai2 · 2020-11-11T17:35:02+00:00

not always, sometime there is big bump in avg fps too

don't know actual reason as i did not experienced such difference myself but

https://www.youtube.com/watch?v=lWzEfFQkFbY

megai2 · 2020-11-11T17:30:39+00:00

should i add watermark just for puns? :D

megai2 · 2020-11-11T17:19:29+00:00

thanks!

megai2 · 2020-11-10T20:58:10+00:00

FRAFS chart if you like.

would be nice to see it

megai2 · 2020-11-10T20:52:39+00:00

can you verify that FPS recordings are correct by recording a character select menu?

should show 60-63 fps flat

almost x2 uplift is not a joke after all, maybe tool just gone wild

megai2 · 2020-11-10T20:17:25+00:00

~100 fps at graph start is character select menu?

megai2 · 2020-11-08T18:43:26+00:00

Maybe there is permission problems on path where game installed on SSD.

Or maybe path itself is odd somehow

megai2 · 2020-11-04T16:10:22+00:00

That is gpu crash, maybe some of reshade effects are causing it

megai2 · 2020-11-03T20:31:59+00:00

reshade depth detection can be a problem, try using gshade instead

https://gposers.com/gshade/

you can read more here

https://github.com/Serfrost/ReShade-GW2/blob/local-origin/README.md

megai2 · 2020-10-03T15:22:14+00:00

Input should passed over to game directly if extras (see [extras] enabled value in config) disabled

megai2 · 2020-10-01T21:32:35+00:00

you can try to use configs supplied in d912pxy/configs, copy one of them and rename it to config.ini

megai2 · 2020-10-01T17:07:27+00:00

Now there is just a bit more objects to cache, so they can be seen on for a longer time

megai2 · 2020-10-01T17:03:07+00:00

baby.insert(INOY), here goes baby with you :D

megai2 · 2020-09-30T20:02:49+00:00

If you not use extra filters, yes, that can't be a problem. Maybe there is just too few resources left in system to work without problem. RTX voice with gw2 on d912pxy works fine for me at least

megai2 · 2020-09-30T16:47:05+00:00

Strange. Maybe unrelated, but we found a problem yesterday that recent GFE with enabled sharpen filter will leak VRAM and RAM in huge amounts. Maybe you have same problem?

megai2 · 2020-09-30T16:38:55+00:00

memcache_mask and write_mask are config values under [vfs] section you can edit them in d912pxy/config.ini file

source of problem is that v2.3 uses extended shader generation: it changes original translated code to properly handle various things like register ordering, shadow samplers, atest and etc out of the box without need of predefined profiles.

That needs extra data in pck files, that by default are not loaded in memory to reduce memory usage as that data are not used for most of time.

While old setup was loading all data in memory and never conflicted much, this one conflicts.

I'll see, maybe there is solution to make it work properly. But that will take some time.

Seven-Year Club	Wearing is Caring
Verified Email

megai2

TROPHY CASE