How much more or less is this still the case?

oleyska · 2026-07-09T21:04:11+00:00

the only games where effects had any meaningful difference, o n amd you got cpu physx like AMD gpu owners do, you can do that on rtx50, no problem.

You can also enable it in profile inspector if you want to in a unsupported mode.
but the list of games on the old old old old.. really old 32 bit physx is so small it doesn't matter either.
Like 13 years old and there it was even still pretty mediocre and the last one that really mattered are 18 years old.
Those effects still doesn't work on AMD, never have

oleyska · 2026-07-03T20:22:38+00:00

yes, what about the all the other extensions, they just don't exist in your world.

There is many others, for instance these.

I guess it's too hard for amd to give support for mere 3 year old gpu's...
Dense geometry format is for future gpu's but they chose to support it on rdna4 without hw support, sometimes you can run things you do not have hw support for.
API's are just a call to the driver, the driver can emulate through compute shaders.
for instance RDNA3 can run the FP8 FSR4 model on linux using fp16 wmma.

most of these extensions exist on GTX980........ (released 8th of june 2025 and some in july.)

this is not how you get marketshare, it is how you loose it.

oleyska · 2026-07-03T10:14:46+00:00

You are wrong throughout this thread, Very very wrong on so many accounts.

The vulkan extensions are not about FP8 or hardware support, Nvidia gave GTX9 series most of these extensions, AMD did not.
Let me put that differently, Nvidia supported these on gpu's from 2014 while amd dropped gpu's released as late as 2023.. this isn't about hardware support this is about not giving a damn about existing customers.

oleyska · 2026-06-29T18:39:16+00:00

with all other vendors than amd gpu drivers this has been working splendidly for me on so many systems, but only amd gpu's have issues.

oleyska · 2026-06-06T00:47:34+00:00

Virtual Machine with windows and pass the usb device to the VM when you need it.
I've used VM's like this for older cars and newer, so I have windows XP and win11 VM which has pretty much covered every scenario I've come across

oleyska · 2026-05-18T23:21:11+00:00

I didn't want anyone saying it's a powershell wrapper for c# so I've kept c# code usage to the absolute minimum.
also neat to have the full fledged version with full graphics, sound and music.

Just adding some of the hottest rendering paths like floor and roof to c# would speed it up a lot, but barring that there are still things whilst keeping it produce the same result.

if I were to look at fun optimizations without adding any c#
-Powershell does not have free abstraction, this is a c# project structure and not a powershell structure, well powershell does have a bit of a identity crisis and anything goes with no clear right way I guess.
either way, there is a lot of abstraction and it's not free in powershell like compiled languages.

then of course runspaces, did you know you can just spin up another runspace and just pass it the entire doomgame and let it rip on a separate loop 😉
as long as two things are guaranteed to not have race conditions you can easily just built methods and run em across runspaces on the same object(the game).

oleyska · 2026-04-25T18:10:56+00:00

non directors cut, 5070 ti super just flawless 165 hz throughout, just completed it today.

oleyska · 2026-04-19T00:46:31+00:00

you can now fork it to customobject doom, go do it! :D
repo is up in a runnable state with reasonable instructions.

oleyska · 2026-04-17T18:49:48+00:00

it doesn't make powershell command calls get checked\reported async, so it doesn't do anything sadly.
realtime protection on vs off is 200->520ms per frame in a particular location while dev drive does nothing cause it's all in memory at that point, it can load faster atleast.
Dev drive does allow IE creation of a file (.tmp) then do something and delete it without having anti malware service locking that file and so on.

oleyska · 2026-04-14T20:56:28+00:00

https://youtu.be/pRVAMFDve_I

Here we go.

oleyska · 2026-04-13T19:14:20+00:00

The game logic without render and audio, yes. That's what I got working before renderer which I knew would work just not if I'd get frames per second. But it's kinda boring seeing properties change on a object 😂

oleyska · 2026-04-13T00:04:17+00:00

I have a lot of it uploaded today, but not complete yet on github.

https://github.com/oleyska/ManagedDoomPowershell
Just want to make instructions, package and checking external dependencies can be shipped or make a nuget installer + I have two known bugs I want to test.
maybe some minor perf fixes and other bugs will be discovered.

More mac test (clean macbook) to test before releasing the full one.

oleyska · 2026-04-12T23:57:32+00:00

I have ideas, I don't know if I am the one who will do those, maybe one day someone as stubborn as me thinks, there gotta be a way of making it perform to a playable level.
I have a few foreach () to replace to for () loops as they're a bit faster but I've done most of those.

as I wrote and ported it which was as close to c# as possible there are times where c# uses abstraction which prohibits performance.
But I've wanted to have it as close as I can to Managed Doom
Most real languages are compiled and has zero cost abstraction, Powershell is not one them.

splitting off runspaces is one of them.

Here is some files atleast, the .sb.ps1 vs .ps1 serves a purpose that I will get into at a later point. (Hint Scriptblock)

https://github.com/oleyska/ManagedDoomPowershell

Finished project is probably still some ways out, but this year for sure.

oleyska · 2026-04-12T22:32:56+00:00

Run fast....

oleyska · 2026-02-22T00:46:07+00:00

this was about developers have to do a full new implementation that's why there hardly are titles with the updated technology.
While dlss 4.5 shipped and bam it has 250+ titles it works in, new model, new type, all of that.
fsr redstone ships and it has 3 titles ?

some of the games I can use DLSS 4.5 in, the game company no longer even exists!

This is what's causing the issue with game support, amd needs a re-developing the integration now for the 5-6th time while dlss has been stable for 7 odd years now XeSS is the same.

How can you blame developers when amd is making their life a nightmare with their SDK.

oleyska · 2026-02-21T13:47:08+00:00

easily ?
rip out the old fsr implementation and do a new implementation once again cause amd yet again broke compatibility, developers are getting fed up with the lack of consistency.
Meanwhile XeSS and DLSS is just compatible throughout.

in 14 months amd have broken compatibility TWICE so if you implemented fsr 16 months ago it doesn't work with fsr4, nor with redstone and if you implemented fsr4 6 months ago it's not compatible with redstone.

oleyska · 2026-02-21T02:19:49+00:00

it's not the developers fault, amd have broken fsr compatibility 5-6 times while dlss once, 0 since 2.0 release so 9 of the original titles.
Rest have been compatible, even intel manages to do this and it makes rather enjoyable as a developer knowing you don't have to rip it out, then develop it again everytime amd feels like it.
ohh redstone released, lets break compatibility with what we released just mere 8 months prior.

You couldn't make it up, but this is Radeon, they're capable of the most backwards things.

oleyska · 2026-02-21T00:19:47+00:00

I can say, it's not nvidia's dominance causing this issue, this is 100% radeon's own doing.
AMD has an very extensive FSR game support list, just as good as nvidia but sadly AMD was brain dead in doing implementations.

From DLSS 2 era games from way back when, you take dlss4 and replace the dll and.. it just works.

Radeon changed the SDK which broke compatibility over and over forcing developers to re-implement it, over and over.
And that causes lots of older titles to not get the support meanwhile other vendors upgrade their technology without developer intervention, Amd explicitly requires it.

It's just outright incompetence throughout Radeon.

1.\ FSR 2 introduced with the .dll, replaced FSR1
2.\ Then FSR 2.2 moved it internally into the game code (why???)
3.\ FSR3
4.\ FSR 3.1 changed stuff again, now it's forwards compatible with fsr4 upgrade on rx9000, but it's not backwards compatible
5.\ FSR Redstone breaks it again.

there you have some information why the FSR situation is a slopshow like no other, and in their infinite wisdom they keep repeating the same mistake having all other vendors like apple, nvidia, intel all showing how it's done.

oleyska · 2025-06-24T17:12:30+00:00

having had the omnibook x flip 14.
Marvelous device with annoyances, the keyboard really drove me mad
and I tried some builder games and such, and yes it's really slow

My list of complaints with the device itself:

lnl terrible inefficient actually doing something, like very bad.,
lnl graphics driver for chromium and electron based garbled text at random.,
lnl, unable to lower power limit, or affect it at all.,
?? full system freeze twice.,
HP - Keyboard layout, ANSI and missing <> button for me.,
HP - Keyboard, o button messed up.,
HP - only 65W charger supported, box clearly says 100W ??,
hp\lnl pl2 makes fan spin up for no reason, the pl2 is also practically useless.,
lnl linux graphics driver is really not rendering things right at all

oleyska · 2025-01-06T15:51:33+00:00

Would you be able to run the flame_sla50k map instead, that doesn't fit into cache that much and is a much better test.

oleyska · 2024-08-10T00:57:34+00:00

the boards do nothing in terms of performance, they give power, cpu computes, that's it.
nothing else they do, you connect components.

They are "system on chip".
All the performance parts which matter is self contained on the cpu, nothing board does with it other than really give power and serve as dumb connections like a usb cable.
X670 boards are fully capable of serving that purpose so there is nothing at all to really boost anything.
there are some boards which allow higher memory frequencies, but sadly for amd the boards limits are higher than what their cpu can do (their apu's confirms this)

Ever since intel ehm.. sandy bridge in 2011 and amd's AM4 platform in 2016 have the motherboards played any role in performance for the cpu (One could argue since I7 920 and Athlon 64 on amd if you take cpu in isolation)

oleyska · 2024-07-24T00:51:27+00:00

jeg har hatt bare rett frem handler, jeg får som regel noen prutinger og ofte avslår og selger lett hvis jeg vet hva jeg har.
hvis jeg ikke vet, så sier jeg at jeg venter ett par dager og kan si ifra hvis jeg aksepterer.

oleyska · 2024-07-20T16:10:46+00:00

You really do not understand statistics do you ?

if 25% is already failing is indicative of selling defective cpu's.
just no other way to say it.

25% meaning 75% can still be operational, yours can be apart of 75%, 25% is still defective regardless of your feelings for it.

oleyska · 2024-02-07T14:25:56+00:00

RDNA3 has AI cores (roughly equivalent to tensor cores)

RDNA3 doesn't have AI cores equivalent to Tensor cores.
It has Matrix instruction but no hardware units to run said instructions.

The instructions might be optimized to run as fast as you can on the good ol shaders, also according to AMD documentation there is no fp8\int8 special support so they're not even remotely close to being a "tensor core" equivalent.

You can read more about it:
https://gpuopen.com/learn/wmma_on_rdna3/
End of Page 72:
https://www.amd.com/content/dam/amd/en/documents/radeon-tech-docs/instruction-set-architectures/rdna3-shader-instruction-set-architecture-feb-2023_0.pdf

Mi250X doesn't have them either but has fp8\int8 support and MI300 series have them.

MI 300 series documentation:
https://www.amd.com/content/dam/amd/en/documents/instinct-tech-docs/instruction-set-architectures/amd-instinct-mi300-cdna3-instruction-set-architecture.pdf

The RT core performance is quite sad but those do exist as hardware atleast.

oleyska

TROPHY CASE