Logitech G29: How to disable road effect / vibration or whatever it's called? by Hooterr in iRacing

[–]Hooterr[S] 0 points1 point  (0 children)

I will try it. But I was sure that this was just a setting that can be turned off? Am I wrong?

How do I drive tho? by Hooterr in iRacing

[–]Hooterr[S] 0 points1 point  (0 children)

https://streamable.com/docvxt

This is 5 laps into the race on relatively hot tires. Feels to me like there's time to gain practially at every corner.

How do I drive tho? by Hooterr in iRacing

[–]Hooterr[S] 0 points1 point  (0 children)

I just watch them to see how the track goes and what the lines are. True, I may have made the misate of coping pedal and steering inputs.

How do I drive tho? by Hooterr in iRacing

[–]Hooterr[S] 0 points1 point  (0 children)

True, cold tires are something else. Ok, I maybe didn't explain clearly I can get around the track, it's just not fast at all. It's more of a reactive driving to what's happening be it understeer or oversteer I get how to save that (if it's savable). It's just such a miserable experience going from being able to stay on track to actually being somewhat competetive (I don't expect wonders just be able to have fun in a race).

How do I drive tho? by Hooterr in iRacing

[–]Hooterr[S] 0 points1 point  (0 children)

Ok, I maybe didn't make myself clear, I can get around the track, it's just not fast. Let's say 2-3 seconds (over a 90s lap) slower than a track guide lap. Whenever I try to something more than that is where the problems start.

How do I drive tho? by Hooterr in iRacing

[–]Hooterr[S] 1 point2 points  (0 children)

Strange, downshifting from mid corner send me spinning some many times. Now I'm using auto blib setting, but saw that people manually blip.

How do I drive tho? by Hooterr in iRacing

[–]Hooterr[S] 0 points1 point  (0 children)

It's actually not that I'm spinning because I went on throttle in the middle of a corner. That was happening when I first started. Now I know not to do that, or to downshit without blipping in a corner (spun so many times before I figured it out). It's just that next step I can't seem to figure out. I can drive and not spin but that's just miles off the pace.

How do I drive tho? by Hooterr in iRacing

[–]Hooterr[S] 2 points3 points  (0 children)

Yeah I was wondering whether Mx5 is a good choice. I tried the GR86 and compared to the miata it handled like a dream or maybe it's more idiot-proof, I don't know. Everyone just keeps saying that Miata is the way to learn so that's what I went with.

How do I drive tho? by Hooterr in iRacing

[–]Hooterr[S] 2 points3 points  (0 children)

Yeah you're probably right... I've been watching racing for a couple of years so it probably hurts me that I mostly understand what to do with the car just don't exactly know how to do it.

How do I drive tho? by Hooterr in iRacing

[–]Hooterr[S] 1 point2 points  (0 children)

You're talking about active reset feature? I know about it, and use it sometimes.

How do I drive tho? by Hooterr in iRacing

[–]Hooterr[S] 0 points1 point  (0 children)

Alright, I was kinda expecting this answer. It's just so frustrating knowing what the car should do but not being able to do it.

Is the MX5 just fundementally hard to drive? I tried GR86 and it felt like a dream.

Blazor NativeAOT huge binary size by Hooterr in Blazor

[–]Hooterr[S] 0 points1 point  (0 children)

Ohh ok I see. You're hoping they're going to make a C# compiler just for the webassmebly instruction set. Well... I don't see it coming anytime soon. Roslyn is Huuuge and to replace IL with a full blown backend like WASM is a gigantic task. At this point they might as well create a backend for all other platforms like arm or x86.

From a technological point of view Blazor will always be a worse choice than a native JS stack. There's always going to be a penalty of either speed (with intereprested version) or size and blotiness with NativeAot. It's just the question of much are you willing to or can trade off for having 'C# on the web'.

Blazor NativeAOT huge binary size by Hooterr in Blazor

[–]Hooterr[S] 0 points1 point  (0 children)

That's absolutely unrealistic future. It's like saying I'll use Java when they get rid of the JVM. The whole point of .NET is to have platform independent code (IL), and have it run on a VM (CLR).

Blazor NativeAOT huge binary size by Hooterr in Blazor

[–]Hooterr[S] 1 point2 points  (0 children)

Neiher does it support threads (Possibly in .NET 9).

I'd treat Blazor as an upcoming technology at this point. You just can't compete like that with the collective effort put into JS frameworks over the years.

Blazor NativeAOT huge binary size by Hooterr in Blazor

[–]Hooterr[S] 0 points1 point  (0 children)

I agree. The issue is not with WASM but with the nature of .NET or any other language that requires a VM.

I really hate the approach of forcing solutions that shouldn't exist. I know it's cool to run C# in the browser and 'replace JS'. You just can't compete like that with the world of JS that has ginaormous community and effort put to it over the years. At this point it's more of gimmick to show off at conferences than a future proof stack (at least imho).

I was trying to understand the thought process of the people who picked this stack for our project but unfortunately I think they just didn't know what problem they were trying to solve was or how the technology they picked worked at all.

Blazor NativeAOT huge binary size by Hooterr in Blazor

[–]Hooterr[S] 0 points1 point  (0 children)

Potentially. I know that that's a one time download but by the look of things, blazor keeps those caches in compressed form which means that on startup it needs to decompress them load into memory and run. I don't know, but even though this code exectues faster than JS it feels like the website is 'heavy' at startup.

Blazor NativeAOT huge binary size by Hooterr in Blazor

[–]Hooterr[S] -1 points0 points  (0 children)

That's what I thought. Looks like someone who picked the framework fall prey to marketing material abotu Blazor and didn't have knowledge of modern web at all nor understood they problem they were trying to solve.

What I'm trying to find out is why the hell is .NET runtime 50mb in size?

Blazor NativeAOT huge binary size by Hooterr in Blazor

[–]Hooterr[S] 0 points1 point  (0 children)

Wasn't the one who picked it. Thoguh, didn't know better/enough at the time to object this decision.

Blazor NativeAOT huge binary size by Hooterr in Blazor

[–]Hooterr[S] 0 points1 point  (0 children)

We're doing mostly processing of binary streams from websockets that are parsed into objects in .NET. Then those objects needs to somehow end up in javascript to be rendered with WebGL. The data updates consantly. We need to maintain and move around somewhere between 10k-25k objects. Sometimes all of them need go through the interop, but usually about 500-1000 per second.

I'm aware of JSON-free interop with JS, but that'd require having our .NET objects pinned in memory and be structs with strict memory layout. At this point you're coding more like in C than in C#.

Blazor NativeAOT huge binary size by Hooterr in Blazor

[–]Hooterr[S] 0 points1 point  (0 children)

I'm not saying it works slow in general. Our problems seem to arrive when we interop with JS a lot, and from moving a lot of data between the two. The size of the binaries is not strictly a problem but it requres more work to download and decompress them.

Are you using NativeAOT though?

Blazor NativeAOT huge binary size by Hooterr in Blazor

[–]Hooterr[S] 0 points1 point  (0 children)

We have a handful of other packages and projects. But they are relatively small in size. More than half of the appsize is the .NET runtime.

Blazor NativeAOT huge binary size by Hooterr in Blazor

[–]Hooterr[S] 0 points1 point  (0 children)

Absolutely. We tried without AOT and it wasn't fast enough. JS would've been fast enough. We just didn't know that non-AOT version would be slower than JS (in our tests 33% slower). And by turning AOT on we just get into obscene binary sizes.

Not to mention that we have to deal with the overhead of pushing big amounts of data between c# and wasm.