Quote:
Originally Posted by manekineko
How transparent would a scaler like that work? Even on the latest kernel, when running something in Nesoid, if it's scaled at all the lag is quite heavy. If it's only doubled (which should really be a very simple operation) the lag is bad, if it's actually scaled to the screen resolution, the lag is really bad.
What're the benefits of moving to a .35 kernel?
Obviously you're always free to work on whatever, but the headset would be an amazing improvement, not just to be able to use it, but since there aren't many other devs that are in a position to work on it.
|
How is Nesoid actually scaling? i want the actual gpu to do the scaling for us not it be handled by a library or android. Android itself will think its running a completely different resolution.
.35? haha.. new kernel. We are running .27 while everyone else is probably running .32. We would run on cleaner code and about 2.5 years worth of improvements. Not to mention bragging rights. You can actually tell someone "your kernel is dog shit.. .35 bitch !!!"
turns our blackstone has headset working, so im going to see if we can use the same code for rhod. Lets cross our fingers.