But will they try to charge you $200 for a cosmetic scratch that now warrants a screen replacement and paying for shipping without fixing the original manufacturer defects?
Xtreme Gamers did a video regarding Asus’ behavior and customer service with their current handheld system. It was not good. The comment is referencing that video.
Because FSR3 is really new, released Sep 2023. Even the games that actually can patch in FSR3 didn’t get to do it properly until Avatar nailed it and just earlier this month released another update to push it further. In short, AMD is working with devs to improve their plugin integration to various engine devs, and I don’t think 3.1 is the “end goal”.
FSR 3’s result really depends on how developer understand and work with the proposed render pipeline compare to DLSS(which basically runs AI kernal to guess what pixel values to fill). Especially with games that features pip scope(fake UI scopes with on the fly fov changes are fine) or some translucent elements where it can not do the velocity buffer properly. (basically most of the fringeness on edge or flickering/swimming are mostly from precision, and ghosting are from wrong velocity when you see the old FSR artifacts).
Pretty much meaningless after TLOUP1 launched as “Steam Deck Playable” and was nowhere near that. I don’t expect FromSoft to screw it up, but the label has been shown to not be a guarantee.
It should help since they’ll be able to hire more people to work on the project. Something badly needed dwith Godot is a proper testing workflow. They currently rely on the community to report bugs, and that’s just not an efficient workforce. Also doesn’t cover all the possible edge cases.
Playing devil’s advocate, I’d argue the in the wild community testing is more likely to uncover an edge case that the formal testing didn’t envisage…? 🤷🏻♂️
I’m with you on that. I feel like open source is the best possible way to security audit and test issues. As any issue will be out there to see, most proprietary code ends ups being years of duct tape which wouldn’t fly if a large community of different backgrounds took a look at the code
To be fair, every single project regardless of proprietary or open source has a backlog like that. It’s just that open source projects show the backlog and don’t have marketing people telling what is and is not in the backlog.
There’s a reliable way to combat scalping in general. Start selling the item at a high price or in larger quantity and then cut the price whenever sales drop off.
Scalpers can only make money by scalping something when it is being sold below what the market is willing to pay for it in the quantity in which it is available.
On a non-economic note, I’d add that I don’t think I’d want to buy an easily-modified Linux computer system from some random person unless I planned to wipe it. How do you know that the thing hasn’t been rootkitted?
There’s a reliable way to combat scalping in general. Start selling the item at a high price or in larger quantity and then cut the price whenever sales drop off.
That alone might be effective at reducing scalping, but would also put the item beyond the reach of entire income classes.
I've worked in camera retail and the local shops do just that, actually, and it's effective. The FOMO people get their stuff first at a higher price, the shop gets a boost in margins, and everyone else gets to enjoy cheaper prices three months later (and have the early adopters sit through the bugs and first-run issues).
Can’t really do that with such a hot product. Would cause too much PR damage and outrage. Companies don’t do it because this way they basically outsource the PR problem to the scalpers while allowing them to play innocent.
The level of outrage over supply issues for a video game console is disproportionate a lot of the time. Outrage that would be better directed elsewhere, but I digress.
That’s pretty cool and I am actually a little excited to try and learn it just for fun. I did very little unity before and godot sounds very interesting
I could also see a database being used to coordinate game ownership with a fraction of the power usage. But neither will happen because consumers always get the raw end of the deal and nothing will ever be done to their benefit without being forced.
But blockchains get “bad” records added all the times. Database entries and blockchain blocks are both equally as susceptible to bad business logic making incorrect entries. No business is going to adopt a sales recording system that doesn’t allow them to control the entries and to reverse the entries they don’t agree with.
Publishers will like a database because it can be modified. If they were forced to implement such a system (thus abandoning all 'sell the same game to the same person twice' for different platforms), they'd oppose a blockchain system hard, since it would make it pricier to:
a) publish seven bazillion versions of any given game
b) revoke ownership of games just because it's cheaper to do that than honor the deal they made with customers
c) correct any data-fuckups they will inevitably make because they went for the cheapest route possible to implement this, and it went pear-shaped from day 3 onwards
I'm very much on the database-side here as well. I work for a Telco company here in Germany, and we use several such databases that are regulated by external bodies and government agencies to communicate between carriers (for number porting and such). Works great overall.
there is nothing wrong with the blockchain. cryptos main problem is the proof of work using to much energy. blockchain to actually do work with the energy it uses efficiently is great.
Go to Platform B and tell them : see, I bought Game already, let me play it here too.
Platform B : “who are you and why should I care?”
Proving your digital ownership never was the problem. The problem is those platforms are different companies and have no reason to honor a purchase from somewhere else.
gamingonlinux.com
Ważne