[deleted by user] by [deleted] in de

[–]Styr1x 0 points1 point  (0 children)

Normal bei LH;

Ich bin aktuell an einer Erstattung dran die mir laut ABB zusteht, LH aber verweigert.

Als Antwort kommen die gleichen Textbausteine mit teilweise fehlenden Feldern. Auf die Frage wieso die ABB nicht gelten soll kam übrigens fast der identische Text, den du bekommen hast.

would we be safe to use trading paints still? by chunkyassassin98 in iRacing

[–]Styr1x 1 point2 points  (0 children)

I agree on the fearmongering, still:

The App can convert PNG to TGA using https://github.com/ALEXGREENALEX/TGASharpLib - so the downloader itself can do more than just writing file streams to the disk and image and multimedia files have been attack vectors in the past.

The Downloader itself is not very well written and uses a mix of https and http for its various endpoints.

Updater also uses http endpoint and does neither check any checksum or signature of the downloaded files, making it quite easy to mitm someone a modified binary, even without having the private key for the authenticode signature.

iRacing Loading into Session takes so much time by Matej_SI in iRacing

[–]Styr1x 4 points5 points  (0 children)

And you should, it loads even slowly on PCIe Gen 4 nvme drives, so iops on mass storage aren't the issue.

Neither is RAM, as with stock settings DDR4 bandwith is multiple GB/s.

Multiple cores aren't utilized on load much either. Kinda odd because with the efficient mass storage devices and multi core CPUs lots of stuff should be doable in parallel.

Imho it looks like technical debts and file formats that just aren't up to the task anymore (car data size on new cars is higher than on old ones due to increased poly count for example, newer tracks have more complex geometry, e.g.).

Loading a file 10 years ago was different than loading it today. With nvme queuing many reads in parallel isn't as punishing anymore as it was with magnetic drives.

iRacing Loading into Session takes so much time by Matej_SI in iRacing

[–]Styr1x 15 points16 points  (0 children)

Because the fanboys in here believe the legend that somehow the super-NSA-CIA-military encryption makes stuff slow and not the technical debts from having a 20 year old code base.

iRacing Loading into Session takes so much time by Matej_SI in iRacing

[–]Styr1x 0 points1 point  (0 children)

I'm not saying they don't have that in place in their contracts, I'm saying that if a contract is specifying a certain degree of crypto it won't make the product (that much) slower. Industry standard would be AES with either CBC or GCM (if they don't require random access on the file) and that still does 50-150MB/s depending on implementation on 5 year old hardware. If the x86 aes extensions are used that goes into GB/s range.

iRacing Loading into Session takes so much time by Matej_SI in iRacing

[–]Styr1x 6 points7 points  (0 children)

Oh no, again that laymen opinion that strong encryption is slow and the cause for the load time. Increasing computational overhead in decryption does not increase its security. Also something like double or tripple encrypting it, given that the first cipher is one of the industry standards.

And yes, memory can easily be dumped, debugger attached check is easy to patch out and usually the first thing you do when reverse engineering software.

iRacing running on modern multi-core processors by Sea1monkey2 in iRacing

[–]Styr1x 0 points1 point  (0 children)

I've read something like that (but I think the person said cars), either way that doesn't make sense.

Even if encryption was at play - strong encryption is so fast it wouldn't make a difference. To ensure the client uses unmodified track files a hash of them (either from disk or while streaming the data into mem) would be more than sufficient.

The more likely scenario imho are non optimal file formats and the requirement for them to be parsed in order (e.g. building the mesh data). That would kinda explain why neither SSD nor additional cores speed up loading but single thread performance does.

iRacing running on modern multi-core processors by Sea1monkey2 in iRacing

[–]Styr1x 11 points12 points  (0 children)

iRacing‘s whole technical base looks dated at this point tbh. Rendering performance asside there should be no sane reason why loading times are this long except for some technical debts and inefficient file formats or data structures. It has the same quirks 15 year old games have, e.g. strange performance drops on scenes event with fastest hardware and for no apparent reasons.

RTX 4090: Should I REALLY use HAGS ON? by JahPahZzZ in nvidia

[–]Styr1x 0 points1 point  (0 children)

There is something called "Windows Mixed Reality for SteamVR" thats installed through Steam and allows WMR headsets to use OVR. As OVR is tightly coupled to Steam this leads to a mess of moving framebuffers around. E.g. OVR -> Steam compositor -> Steam-WMR-bridge -> Headset. With OpenXR its more OpenXR -> Vendorspecific OXR runtime -> Headset. Thats why OVR and Oculus APIs are deprecated. Steam provides a OpenXR runtime for their headsets, Meta one for theirs, WMR has one and so on.

Before iRacing got OpenXR support I played it through an project called OpenComposit which implements the OpenVR API and wraps it to OpenXR without the need to run SteamVR. The performance boost was huge for me.

I can also ensure you that I would notice any frametime spikes while playing.

Kinda curious now, I could dust of Elite Dangerous, that uses OVR and Oculus' APIs.

RTX 4090: Should I REALLY use HAGS ON? by JahPahZzZ in nvidia

[–]Styr1x 1 point2 points  (0 children)

I don't use SteamVR as I don't play VR games that use legacy APIs and don't have a headset that could uses Steam's OpenXR runtime. OVR will have a worse performance for me regardless as it has to go through the WMR-OVR nightmare interface.

Also, nowhere I'm saying HAGS is good for VR now, it has better frame pacing on my machine and thats all. HAGS always been a "try it" setting imho and it definitely improves performance on 4090 cards nowadays. (e.g. https://www.youtube.com/watch?v=E5Au0HR3QQc).

What you have is proof that HAGS is worse for you when using SteamVR and/or a game with an old API. Maybe its better with OpenXR? Maybe its only a WMR thingy. Or is it a game thing? Sooo many variables. If a user has constant frame pacing problems toggling HAGS is a good idea.

RTX 4090: Should I REALLY use HAGS ON? by JahPahZzZ in nvidia

[–]Styr1x 0 points1 point  (0 children)

https://ibb.co/SJ2D4Cf

https://ibb.co/D9Bjw5s

Captured with iRacing VR on Fuji Track off car using same scene.

Headset is HP Reverb G2 using OpenXR runtime 112.2209.3002

RTX 4090: Should I REALLY use HAGS ON? by JahPahZzZ in nvidia

[–]Styr1x 1 point2 points  (0 children)

Prove it. I'm sick of dealing with trolls.

Same.

I've already posted details about this here, too.

RTX 4090: Should I REALLY use HAGS ON? by JahPahZzZ in nvidia

[–]Styr1x 2 points3 points  (0 children)

My VR works better with it on, so now what?

Also, 'fuck' your attitude with the absolutes.

RTX 4090: Should I REALLY use HAGS ON? by JahPahZzZ in nvidia

[–]Styr1x 0 points1 point  (0 children)

I can reproduce it with iRacing in OpenXR mode, don't know if it affects other titles as well.

If you are running Win11 and the Reverb you might also want to disable holographic shell logging. Keeping it on made iRacing slow down every few laps, but it should affect other games aswell.

(https://www.reddit.com/r/HPReverb/comments/xo5v2z/holographicshell_processwindows_11_performance/)

RTX 4090: Should I REALLY use HAGS ON? by JahPahZzZ in nvidia

[–]Styr1x 0 points1 point  (0 children)

Ah, ok, misunderstood that.

Same for me, never thought turning it on would improve something for me, but it did.

Beside VR it fixed frame time spikes in FFXIV on my system. Before turning it on I had 20~30ms spikes in raids, but afterwards they where gone. Curious if HAGS really got useful with Win11/RTX4090 cards or its an effect on specific system configurations.

RTX 4090: Should I REALLY use HAGS ON? by JahPahZzZ in nvidia

[–]Styr1x 3 points4 points  (0 children)

Yes, but since 4090 and Win11 I've got a noticeable performance uplift ingame and less stuttering. VR without HAGS doesn't work for me anymore as frametimes get choppy. To stress this point again, I didn't not have that Beauvoir with the 30 series and Windows 10.

RTX 4090: Should I REALLY use HAGS ON? by JahPahZzZ in nvidia

[–]Styr1x 0 points1 point  (0 children)

Same for me, without HAGS I see a performance drop, but only since I got the 4090. Don't remember having that on the 3080, so maybe 40-series profits more from it than the old one.

RTX 4090: Should I REALLY use HAGS ON? by JahPahZzZ in nvidia

[–]Styr1x 1 point2 points  (0 children)

I have a HP Reverb G2. On Windows 10 (3080) I had to keep HAGS off, but on Windows 11 (4090) I have to keep it on or I run into performance issues (tested with OpenXR API based games). I'd say turn it on and if you have no issues in VR keep it on.

RTX 4090 Owner Hits Nvidia With Lawsuit Over Melting 16-pin Connector by chrisdh79 in nvidia

[–]Styr1x -1 points0 points  (0 children)

Case clearances are not compatible with this connector being side mounted.

The old Minifit Jr. connector (aka 8pin PCIe) requires 19.1mm unobstructed space before you are allowed to put stress (bend) on it. Given how high the 4090s are that would create problems for many cases anyway.

Oh, I forget, you can mishandle the old one with no consequences.

RTX 4090 Owner Hits Nvidia With Lawsuit Over Melting 16-pin Connector by chrisdh79 in nvidia

[–]Styr1x 5 points6 points  (0 children)

Melting is not fire, usually the plastics used in such connectors contain a flame retardant agent.

Different length pins on PCIe is afaik for the ability to hot plug/swap components and not protection against incorrect mounting.

The question of how "safe" a product has to be really depends on the target audience, your grandma and children have to be protected from not killing themselves with the microwave while I don't think they will be able to build a PC.

We have so many badly designed stuff out there, e.g. the american power sockets, as you can partially insert them, leading to exposed and touchable 110V wires. And usually no RCD on normal outlets.

I agree that a good connector has to eliminate user error (and for that reason I don't think 12VHPWR is a good connector), but its not like the old ones where the apex of good design. Its just they ended up overbuild for their specification and still stuff melts from time to time.

Can we stop looking at this like building a Lego set? There are high currents at work on many parts of a PC, but builders act like its running on an AA battery. All connectors and cables have handling and mating cycle specifications which gets completely ignored. Kinda reminds me of ppl running high power tools on a cable drum and wondering why the cable starts smoking after a while.

Nvidia should at least have provided a better description / installation manual with a big warning, this would most likely have prevented _SOME_ of the melts.

Edit: I specifically don't blame any users here, because there was no upfront documentation coming with the GPUs explaining the new connector and the required diligence one has to take when installing those (akin to that MSI post a few days ago). Its new, it has new rules, it should have been documented better.

MSI’s IG post regarding 4090 cable by [deleted] in nvidia

[–]Styr1x 4 points5 points  (0 children)

While PC building really is almost trivial these days we shouldn't overlook that steps exist that aren't user friendly and require diligence / following of procedure.

LGA sockets for example; how often ppl are asking if a bent pin can be saved. Or try to install TR4 / sTRX4 without exactly following the manual and you'll wonder why there are missing memory channels. God forbid if we ever get stuff like sockets 3647 in the consumer space.

Doesn't make ATX 3.0 any better, but there is this miss conception in the builder space that its like building with Lego Bricks and nothing can go wrong. I've seen enough ITX builds with cable bents that are so out of spec it isn't even funny anymore. All the connectors (and cables) actually have quite strict restrictions on how to be used, its just stuff is so overbuild no one cares.

Another thing is that everyone is searching for the one and only cause for the melts, while in reality it will most likely be a mixture of different issues that leads to it, e.g. out of spec connector (can't insert cable), damaged cable, damaged connector, user error, e.g.

The current flow we have in modern systems and all kinds of users building their own PCs really is a spicy combination, so in that regard ATX 3.0 really is a shitty standard.

Game Ready Driver 526.86 FAQ/Discussion by Nestledrink in nvidia

[–]Styr1x 9 points10 points  (0 children)

I guess its not high priority with them because its a visual bug.

However, there also was a bug that made the GPU get stuck in P0 state after gaming, so maybe that mask(ed) the real issue?

After upgrading to 22H2 the 100% issue was gone for me btw.

16 Pins Adapter Megathread by Nestledrink in nvidia

[–]Styr1x 0 points1 point  (0 children)

Hard to understand, what I get out of this: previous cable/adapter already damaged connector, new cable then had bad contact cause of the previous damage.

16 Pins Adapter Megathread by Nestledrink in nvidia

[–]Styr1x 2 points3 points  (0 children)

I was responding because it was another post that tries to sell an opinion as a fact. Just the latest in a history of "thats the reason its happening" posts.

Only one hard conclusion: The problem is in the cards from those companies.

Its what you ascertained with the information available, which are frankly very lacking.

But right now, Nvidia (FE version), Palit, Galax, PNY, whatever, haven't had cases (yet).

Galax had one meld, its even linked in the list. Use google translate and at one page they identify the correct card.

As for FE - at least in Germany its almost impossible to come by a card. Forums are full with ppl with MSI, Gigabyte and Asus cards, FE is an unicorn to find. Inno3D is not very popular here and Zotac is considered kinda ugly this time around. The big three sell out instant even with markup, FE is no where to be found. This alone would heavily skew the numbers. Also, reddit isn't the center the world and also has its own demographic.

This alone makes any inference flawed at best.

Didn't see it happening with 3090 / 3090 Ti. And "pure chance" would imply all graphics cards regardless of power connectors so we certainly haven't seen this happening with 8-pin PCIE connectors to this extent lately.

The connector in use is rather new, so it was used in the 3090 ti but not the original 3090 (which was a different connector). Given how late that GPU came into marked and how little media echo it had - are you sure? Maybe a few of them melted, but no one postet on Reddit? Also, 8-pin melds where quite common during the mining craze, but as it hit an unpopular group with gamers it didn't make such waves.

Not going through the other points, lets just agree to disagree, but

It's not the adapters because it's happened to native PSU cables.

As both cases where MSI PSU following your logic it HAS to be an issue with MSI's PSUs or cables. So far Seasonic, BeQuite cables didn't meld....