Sniperfox47

The title of this thread is *incredibly* misleading.
 
As has been mentioned you buy a lisence to the software, *not* the software itself. Software is code and code is IP. It's no different than a book. When you buy a book you're buying an instance of that book. You aren't buying the book itself. You can't then go and make copies of that book or do other things that act against the book owners copyright, trademarks, or patents. Owning a copy of Red Fish Blue Fish doesn't mean you own Red Fish Blue Fish itself. You're buying the goods, not the IP associated with those goods.
 
*No* country equates selling a copy of a game/movie/music/book to selling the game/movie/music/book itself. Period. That would have massive sweeping consequences to other IP law and would defeat the whole point of IP law.
 
And before you say "well that's just semantics", yes. Yes it is. It's legal semantics and it's what these words mean in a context of ownership. At the end of the day all discussions of what a thing is are inherrently arguments of semantics so using that as a deflection is kinda silly.

Really interesting how the 360 rad was "beat" (by 2 degrees) by the 240. Kinda curious on what happened there. 

I don't get why a 360mm AIO performs worse than the 240mm version. I assume the pumps and fans are the same in both models. So the only difference is the size of the rad. How??

You mean VS all the stuff that Linux has that Windows is missing, as @pipnina mentioned? Or you know, the whole benefit of Linux where you can just choose a different desktop compositor that has the features like that that you need?
 

 
Umm your file manager doesn't do any of the searching for SMB shares, Samba and NetBIOS do. It sounds like you picked a distro with a crappy SMB preinstall. There's a reason why new users should either be using Ubuntu if they're a basic user, Fedora if the're a developer, or SUSE if they're crazy.
 
A) The quote that you quoted was about WINE and none of this has to do with WINE.
B) What are you even talking about? Intel, Valve, AMD, and hell even Nvidia have been making huge inroads into improving drivers and stability for gaming... There are massive changed to the backbone of the Linux kernel going on *right now* to make it fundamentally better for VR than *any* other OS on the market, in that the whole display stack is being reworked from the ground up with VR in mind. Do you follow along with any linux related news at all?
 
You really have no idea what you're talking about on a lot of this stuff. Do some research on Phoronix into the *massive* changes happening at low levels in the Linux kernel. The push by Kronos members to build out a strong API ecosystem around Linux and cross platform development. Linux already is a *more than decent* gaming OS. It performs better in a lot of cases than Windows... even many times now with games originally designed *for* windows.

The title of this thread is *incredibly* misleading.
 
As has been mentioned you buy a lisence to the software, *not* the software itself. Software is code and code is IP. It's no different than a book. When you buy a book you're buying an instance of that book. You aren't buying the book itself. You can't then go and make copies of that book or do other things that act against the book owners copyright, trademarks, or patents. Owning a copy of Red Fish Blue Fish doesn't mean you own Red Fish Blue Fish itself. You're buying the goods, not the IP associated with those goods.
 
*No* country equates selling a copy of a game/movie/music/book to selling the game/movie/music/book itself. Period. That would have massive sweeping consequences to other IP law and would defeat the whole point of IP law.
 
And before you say "well that's just semantics", yes. Yes it is. It's legal semantics and it's what these words mean in a context of ownership. At the end of the day all discussions of what a thing is are inherrently arguments of semantics so using that as a deflection is kinda silly.

Actually, for many people that face eye problem, PWM or the flicking of the display (for the case of CRT) is the main cause.
In the old days, most consumers and office bought the cheapest CRT monitor, which could only go to 60Hz, and used horrible phosphor layer creating a lot of flickering. 60Hz flicker is crazy annoying. Today, the issue is monitors using PWM circuit to save money (or power in the case of mobile devices), instead of using a dimming circuit. These flicker are based on the screen brightness. Some people feel a sign a relief when they set their screen brightness to 100% (which turns off the flicking from PWM circuit) despite having their eyes hurt from the strong brightness of the screen.
 
The same problem applies with CFL powered backlit monitors, and even CFL lights in office. The crap one flicker due to the poor layer of phosphor in them, while the more premium ones don't (and that is aside terrible CRI level the cheap one can produce affecting the color of everything... but that is a different topic and not related to this issue)
 

I think this will encourages racism. You are given a choice to pick the better color.
To solve this, it should show all colors, RGB rainbow style, including IR... we can't discriminate against it.

I'm going to reply just to this because it is indicative of the communication issue we're having.
 
If you're going to talk about how ethics is an important part of psychology, please read a psychology textbook. Even the basics used for psychology 101.
 
Rationalization, the term *you* used has nothing to do with rational thought or being rational. Rationalization is specifically that psychological quality of using a dissonance as a defence mechanism, that's what rationalization means. It means justifying something irrational as being rational, hence the suffix at the end which means "to make as though" as in "to make as though rational".
 
The logical fallicy of rationalization is *directly* related to the psychology term rationalization.
 
Technical language exists because it is a consistent common basis for which to build discussion and debate. You can't have your cake and eat it too, calling out things as not being technically true based on the colloquial meaning of a word used out of context. If you want to argue sociology and psychology I'm happy to do so, but not if you're going to disregard the platform of understanding in those fields.

What are you even talking about? Having that car is not a right... Being alive is a right. You don't have a right to have a car. But even if you did your logic is totally baseless because self driving cars are provably less risk to civilians than cars driven by people, unless they're made by Uber. By that logic you should take away everyone's drivers lisence and shut down Uber's self driving program before you even consider shutting down the other major self driving players.
What are you even talking about? No it doesn't...
 
Arbitrary is the Latin word Arbitrarius coming from the latin word Arbiter meaning "one who judges or dictate". Arbitrary is a thing that is dependent on ones personal judgement or reasoning as opposed to fundamental principles of nature or logical reasoning...
 
If morals and ethics are decided on personal whim and the influences of society they are the very definition of Arbitrary... That's what the word means...
 
Them being different is not the reason they're flawed, them being totally independent of any principle or logical reasoning is why they're flawed. Humans are flawed creatures, anything we determine by virtue of our own agency is likewise flawed, again by definition...

People are forgetting that just because he had a sexual encounter does not mean he broke the law or enough company policy to legitimize sacking him.  But for the sake of PR they had to do something.  In the corporate world (in fact any world with contracts on that scale) you have to either proved illegal misconduct which undermines the contract or you have to pay them to go.   It is actually the foundation of innocent until proven guilty and people should be supporting it not crucifying them for it.
 
 

It's using the audio codec (DAC/ADC/Encoder/Decoder) in the SoC just like a lot of high end phones so the most likely probability is that they just built the sample release with it running in a lower than native sample rate. A lot of these tiny integrated ADCs have issues when recording at low sample rates, adding a lot more electrical noise then they otherwise would when they downsample.
 
A number of my smaller USB DACs have similar issues if they're doing the upsampling.

It's using the audio codec (DAC/ADC/Encoder/Decoder) in the SoC just like a lot of high end phones so the most likely probability is that they just built the sample release with it running in a lower than native sample rate. A lot of these tiny integrated ADCs have issues when recording at low sample rates, adding a lot more electrical noise then they otherwise would when they downsample.
 
A number of my smaller USB DACs have similar issues if they're doing the upsampling.

Because other than this, their quality is unmatched and everything was literally perfect so this was naturally the highest priority.

There's a pretty big difference between a lineage OS kernel and an actually chipset OEM validated board support package though. Sure those phones may be getting security updates for userspace (relative the Linux Kernel) stuff with ART or whatever, but that's really just a false sense of security.
 
The actual parts of your device that an attacker wanting to cause serious harm will use are things like radio firmwares, chipset drivers, and proprietary kernel modules. These things are *not* getting patches because the OEMs aren't releasing patches.

There's a pretty big difference between a lineage OS kernel and an actually chipset OEM validated board support package though. Sure those phones may be getting security updates for userspace (relative the Linux Kernel) stuff with ART or whatever, but that's really just a false sense of security.
 
The actual parts of your device that an attacker wanting to cause serious harm will use are things like radio firmwares, chipset drivers, and proprietary kernel modules. These things are *not* getting patches because the OEMs aren't releasing patches.

Probably not. Very very few games support 3D Vision officially, it's basically a dead product at this point.
 
There are some hacky workarounds you can sometimes do, but do note that they likely won't work with any game using DX12 or Vulkan.

That doesn't show any drivers. It's just a list of your PCIe devices. You need "lspci -v" to see attached drivers.
 
The driver should either be ATI/Radeon, fglrx, or Catalyst Legacy.
 
Those drivers are not compatible with his GPU. His GPU Is Southern Islands based and would need an old legacy versiuon of Catalyst if he wants to use proprietary drivers.

depends on if your phone is rooted. If Rooted you can use Aparted. If not then no. Android restricts low level storage access to the SD card to prevent random apps reading your data.

@uzivkovic997 Which version of Ubuntu are you on? Some older cards don't work very well on 16.04 or 16.10.
 
Which graphics card driver are you using, since older AMD cards have several options available with different acceleration packages available for them.
 
This looks like an issue with VDPAU and VAAPI not having the proper driver links since those two things are responsible for video acceleration. You can confirm this with the "vainfo" and "vdpauinfo" commands in a command line. It'll spit out a bunch of junk which you can mostly ignore. If it gives you an error then it's not working, if not then it should be working. The error for vainfo would look something like this:
 
It's probably just one of the packages you need not being installed by default. Unfortunately you have a card from just before a lot of these issues got fixed with the new unified AMD drivers.

Use it.

Mine was on by default and it was kind of more of a PITA than a help because all my main OS drives were showing up as removable in the OS and got mixed in with flash drives and stuff when I went to unmount. It's easier to have it off and turn it on for the drives you need, than to have it on and turn it off for most of your drives.

The TP Cast Wireless kit has a transmitter that plugs into your Vive's link box, a router that you connect via Ethernet  to your desktop or laptop (you can a USB to Ethernet  adapter if you need) and a reciever that plugs into the headset itself.
 
It uses the standard HDMI and power connections from the link box for the transmitter. That that uses WiGig to send video to the headset and doesn't rely on WiFi at all.
 
The USB data though is transmitted back to the computer via a specially set up router (included in the package). I don't know why they used this route but it's kind of awkward. As said you can use a USB-Ethernet adapter to plug it in. You need to configure a local link between your PC and the router (they give instructions for this) and then set up their software that decodes the Ethernet frames back to actual motion data. This uses a 5GHz WiFi connection for some reason.
 
Like I said, it's kind of awkward to set up and isn't quite as fluid as the official adapter, but it doesn't require anything other than normal Vive stuff and an Ethernet connection.
 
 

Considering it's literally just the developer options notch testing at the moment and the phone isn't officially released yet, let's hope that prior to launch they actually add a proper option in settings that makes it behave like other phones, using the notch exclusively for time, status, and notification icons but otherwise totally black.

This is a good PR move. We'll see how it plays out in the long run though. Microsoft has done enough abusive crap to the open-software and hardware communities very recently that this isn't going to make me lower my guard in the slightest.
 
Biggest question is what all patents were contributed? That's a lot of patents but if they're mostly trivial or if they impliment things dependent on other closed patents, it's naught more than a show for PR.
 
I really hope that this is them honestly commiting to open and collaboration focused development. 

If it's a 180 pixel high cutout, leaving the full 16:9 screen, was totally bezeless, and had a webcam, IR Sensor and Mic in the notch I'd actually be totally down for that.
 
I miss 4:3 displays and anything that gets me a little closer would be nice.
 
The bezelessness would make it easier to run multiple of them side by side and would improve the effect of my Bias Lighting.
 
And the extra junk in that cutout is a small price to pay for cutting out the middle part of the taskbar, a part of the taskbar I never use. It just means I don't have to set the taskbar to auto-hide.
 
A perfectly valid workflow can be built that incorporates the display Cutout, so long as it's adding to the real estate and not subtracting from it.
 
It's really not. The difference between a 24 inch and 27 inch display is 3 inches. The difference between 5 inches and 5.5 inches is literally half an inch...