Yeah it was not a surprise, and I understand someone has to pay for the bandwidth those features use up. But I still resent them for making remote start app-only.
I am otherwise happy with the car itself, but this does leave kind of a sour aftertaste. I feel like it’s only going to get worse with my next car…
Subaru does the same thing, on my car it was free for three years then you pay or lose all connected features. That includes remote start, there is no way to start the car from the keyfob.
If this was a YouTube thumbnail, it would also have a stupid arrow pointing to it and a mind blown (or smiling poop) emoji. Maybe some fire too? Oh, a trash bin, of course!
Sad times…
My mistake then! Except for the 486 series I was strictly an Intel kid. I guess we often forget that AMD is the one who “won” the 64 bit war.
I have fond memories of writing interrupt handlers (staying on topic…) and using Soft-ICE on my side monochrome monitor to debug them. Good times!
What bothers me the most here is that those are 64 bit instructions, which did not exist when PS/2 was a Thing. But I still chuckled, nice work.
Back then our registers were 32 bits wide, and we liked it 🤣
You'd just point yourself in a random direction and see what popped out as interesting.
Fallout 3 was the same, and I loved this so much. Somehow they failed to keep this up with 4 (I never played 76).
I guess they felt like worlds you were a part of, rather than the center of. So many things to discover!
Vulkan and DirectX could already share shaders, because the input for both was already HLSL. The difference is the intermediate representation of the compiled shaders that will now be the same in the future (SPIR-V for both).
The real winners here are driver programmers at NVIDIA/AMD/Intel, since they will no longer have to develop support for both DXIL and SPIR-V (which are similar in concept but different in implementation). How much of that will be true in practice remains to be seen, but I am hopeful.
There are tools to analyze, process and transform SPIR-V bytecode already, presumably those will work for DX12 shader model 7 too. It might make performance analysis easier, same with debugging via a tool like RenderDoc that supports SPIR-V but not DXIL.
As for the overhead of DirectX, with DX12 this is largely not true anymore, both are high performance APIs with comparable overhead (i.e. as little as possible).
Amazon is a prime example
I see what you did there…
I remember your previous post, congrats on not giving up.
Whipping up a script to solve a very specific problem is super satisfying, but I found that anything you write quickly becomes a liability. Debugging Perl can be super difficult, especially when returning to something you wrote a while back.
Personally I grew tired of the punishment and left it all behind! If I need a quick script I’ll use Python instead, and if it doesn’t work I can use a real debugger to fix it.
In any case it’s always fun learning new things, I hope this experience ends up being useful to you in the future and you get to easily solve a problem that stumps everyone else involved.
Cheers!
some people on IRC
Well there’s your problem! (just kidding)
Honestly though I don’t know why you would pick Perl unless you want to learn an obscure language that is both painful to read and write. May $deity have mercy on your soul.
I was quite amazed reading NopHead’s blog a while back because he uses OpenSCAD exclusively, even managing to design an entire printer and its upgrades in there. I didn’t think any sane person could do this.
That is my recollection as well. Also I remember Psycho Mantis would make some comments about the content of your memory card before the fight.
Another favorite of mine is The End in MGS3: Snake Eater, he is a sniper hiding in the woods and it takes like an hour of game time to beat him down. I seem to recall if you save during the fight and change the date forward a few years on your PS3, when you reload he has died of old age waiting for you to come back.