We bought a sodium battery for our last trip, and it turns out that most airline companies don't even know what sodium batteries are and don't have any provision in their regulations, they are as restricted as lithium batteries :(
The problem I'm pointing out is that it's a work based on a Valve property that fundamentally cannot be tied to the DRM because it's "just" a ROM.
I believe this came up when the creator was talking about libdragon-- Valve has been more forgiving of other games like Hunt Down the Freeman and whatnot because they're native executables with the Steam DRM, which video games based on Valve properties necessarily must have. Portal 64 simply cannot do this, because Steam is not a Nintendo 64 application.
I am currently living in Japan, and it seems that they follow the American style exams. I don't know if it is a result of the post-war occupation, or it was already like that before WW2.
Back home in Spain we follow the same style of a single national-level exam that you mentioned though.
That's quite impressive. 70% is obviously way too big for a MiSTer core, but I wonder if one day we will have an affordable FPGA board able to simulate a late '90s PC...
> Also it had forward texture mapping which significantly improves cache utilization and would be beneficial even today.
Not really. Forward texture mapping simplifies texture access by making framebuffer access non-linear, reverse texture mapping has the opposite tradeoff. But that is assuming rectangular textures without UV mapping, like the Sega Saturn did; the moment you use UV mapping texture access will be non-linear no matter what. Besides that, forward texture mapping has serious difficulties the moment texture and screen sampling ratios don't match, which is pretty much always.
There is a reason why only the Saturn and the NV-1 used forward texture mapping, and the technology was abandoned afterwards.
It depends on your use case. Storing WGS84 coordinates as 32-bit floats can incur on errors of several meters. It might be good for your fitness tracking application, but not for serious GIS usage.
Case in point: many years ago I was working on some software to generate 3D models from drone pictures. The first step of the pipeline was to convert from WGS84 to ECEF (https://en.wikipedia.org/wiki/Earth-centered,_Earth-fixed_co...), an absolute Cartesian coordinate system. Well, it turns out that at the scales involved, 6.371 million meters, 32-bit floats have a precision of half a meter, so the resulting models were totally broken.
Isn't that more of using a float to represent the number? Would be akin to trying to represent .5. Which, if your goal is to represent decimals, you are best off not using floats.
Granted, just storing it as a 32 bit integer is probably difficult for most uses. BCD just isn't common for most programmers. (Or fixed point, in general.)
You should be able to do the calculations in fixed point, easily enough? Indeed, it used to be that most embedded systems would use fixed point due to lack of float hardware.
I would actually think fixed point would be beneficial for its accuracy being a bit more controlled than floating point is. Yes, you lose the range of floating point. But I just don't see how that is relevant for numbers that are constrained to +/- 180 by definition.
That all said, I cannot and do not argue against that it is faster to get going with basic float/doubles, due to how commonly those are supported in base libraries.
> For example, one-third of the top 100 mobile games in Japan currently come from China.[20]
China is indeed taking the mobile game world by storm. Go to Akihabara and you will see these huge billboards of Chinese games like Genshin Impact or Honkai Star Rail. China is starting to outplay Japan at their own otaku game.
I live in Japan and IMHO the problem is that it is an extremely conservative and risk averse country, "if it ain't broke don't fix it" taken to the extreme. They had a period of innovation after WW2 out of necessity, but after the bubble crash of 1990 they reverted back to their old selves.
reply