All mainstream headsets get open-source drivers eventually: https://github.com/collabora/libsurvive
750 karma · joined September 11, 2015
All mainstream headsets get open-source drivers eventually: https://github.com/collabora/libsurvive
1) The stack is mature now, we know what features can exist.
2) For me it's about having the same stack as on a 3588 SBC, so I don't need to download many GB of Android software just to build/run the game.
The distance to getting a open-source driver stack will probably be shorter because of these 2 things, meaning OpenVR/SteamVR being closed is less of a long term issue.
Unless the lenses/displays are bad, but I figure we would have heard by now?
As long as your bottom dependency is fixed, you cannot progress!
They should only ban consuming. (impossible I know, but that hints to the real problem)
Kids need to create.
That way you are saving 10x electricity AND moving away from M$ in one blow.
Then stop using closed source software, and start releasing your software as open or source-available.
And I promise the world will become a more peaceful place, slowly then all at once.
https://multiplayeronlinestandard.com/goto.html (the reason for the domain is I will never waste time on HTTPS but github does it automatically for free up to 100GB/month)
Or 169MHz if meshtastic supports it? Edit: Seems no, sadge.
If you add EU freq. I will buy!
Is there an assembly application planned or will it be basic for now?
Solution is to remove some files... and pray it lasts half of a 64GB Intel X25-E!
It should last 30x shorter because it is 30x larger?
Or is this game only about saturation rate?
Edit: Made a 30MB png with linear interpolation (because I don't have all day): http://move.rupy.se/file/turgot.png
Here's another map of Paris (this time with interpolation): http://move.rupy.se/file/eau_paris_3.png
Though you'll need USB hub for internet (WiFi/Eth adapter) and audio.
Also shipping takes a few months, which is kinda scary when you don't know the tariffs that far in advance.
Also Netty is one of those middleware "pretend to help but really bloat" libs.
I would sincerely recommend to avoid those as implementing on top of lower common denominators always is faster in the end after all the Netty bugs have been sorted.
For me I have been waiting for them for 20 years, as the blocking IO made MMO development impossible.
In the meantime we got NIO in 1.4 that only became performant and stable around 1.7 so it's been a slow progress.
I dug out my old blocking server code from back then and with a fresh coat of paint I'm ready to let the non pinned VT's rip and compare them to the NIO backend!
The trouble starts when you want to provide ALL domains I guess. I wonder what database would be best for that; just MySQL with int to name table?
The trouble with DNS is that you need a fixed external IP that has port 53 open.
Not easy to get at home cheaply.
J2ME > J2SE > J2EE (that I never used)
The JVM is the final emulator.
I think everyone should write their own minimal JVM before judging?
The 3588 that can play HL2 at 300 FPS draws maybe around 10-15W.
Windows is 99% of the market today so if you don't support it you don't exist, in 5 years I'm hoping Windows will be around 50% because people will grow tired of the violent AAA games and electricity prices will rise.
Playing a couple of hours will soon cost more than the game costs to buy.
Thinkpad X61s(45nm) DDR2 / D512MO(45nm) DDR2 / 3770S(22nm) DDR3 / 4430S(22nm) DDR3
All still in client use.
All got new RAM this year and when the SSDs break (all have SLC) I have new SLC SSDs and will install headless linux for server duty on 1Gb/s symmertic fiber until the motherboards break in a way I can't repair. Will probably resolder caps.
But had to upgrade to 3050 because 2GB VRAM is to little for modern titles.
Fun fact: One 6600 core can saturate the 1030 for skinned mesh animations.
But only saturate the 3050 50% = perfect because the world takes much less CPU (you upload it to the GPU and then it's almost one drawcall; more like one drawcall per chunk but I digress) = OpenGL (ES) can render on it at lower motion-to-photon latency without waste = one core for rendering, one for gameplay, one for physics and one for the OS, audio and networking.
So 14nm 6600 + 8nm 3050 is actually the combination I would use for ever.
HL:A runs at 90 FPS with that combo too on the low res Vive 1.
Not that VR is going anywhere, but still peak demanding application.
As I said the X86 would use linux but as a server, not a client.
A server has to handle thousands of clients and then it's ok to have the extra power.
I don't understand why you think the last sentence, it makes no sense:
I am encouraging people to get low price, low power, open hardware and software for everyday use before the KWh goes to $1 which is HAS to do, hopefully not too soon.
So I do not want people to only move to linux (on their X86) but also move to ARM/Risc-V.
Directly from Windows on X86 to Linux on ARM/Risc-V in one go.
Two flies with one hit.
That said all X86 should become linux servers = this is only valid for the client.
You can only stream 720p out at 20 FPS from my 2711 though, so it only seems to decode well = watching/consuming media. (the future is producing)
The 2712 can stream out 720p at 40 FPS. (CPU)
The 3588 can stream out 720p at 60+ FPS. (CPU)
Edit: HL2 runs at the "same" FPS on each (sometimes 300+ on 3588)...