00:44RSpliet: karolherbst: if you were referring to the box in the right-click menu for game -> Properties -> Set launch options... that doesn't work
00:44karolherbst: RSpliet: well, it does for me
00:44karolherbst: RSpliet: what exactly did you put in there?
00:45gnarface: i thought you have to literally call bumblebee in there too
00:45karolherbst: there _has_ to be a string like %command% in it. Otherwise everything you put in there gets added to the end of the invocation
00:45RSpliet: ah ok
00:45RSpliet: that explains
00:45gnarface: RSpliet: note "%command%" literally, it's parsed by steam before the command gets sent to bash
00:46karolherbst: so like for doing prime offloading I need to put in this: DRI_PRIME=1 %command%
00:46gnarface: there's a couple others that are useful but they all work like you'd expect if they were coded by windows monkeys with 0 unix experience
00:48gnarface: (finding explicit documentation on it is damned near impossible too)
00:52RSpliet: yeah that's all better
01:05RSpliet: Now at least I know neither portal nor dota 2 benefit from the insn scheduler I've been testing so far
01:06gnarface: what type of framerates you getting?
01:07gnarface: i'm just curious
01:08RSpliet: On a GT940M
01:09RSpliet: Portal 51.7fps, DOTA2 ~38fps
01:10gnarface: ouch, compared to the proprietary drivers
01:10gnarface: but still, i'm impressed you got it working
01:10gnarface: that's totally playable
01:10gnarface: did you try it from big picture mode too?
03:10rhyskidd: any reviewers for https://github.com/envytools/envytools/pull/106 ?
03:11rhyskidd: register name comes straight from the limited hw documentation
03:48imirkin: mwk: did nv4/nv5 not do lines?
03:48imirkin: (or points)
10:23mwk: imirkin: yeah, no lines on NV4 or anything newer
10:23mwk: you can only use lins
12:21RSpliet: gnarface: this GPU is not to be compared to on-line benchmarks. Wikipedia does not acknowledge the existence of my 940M, considering it's a GM107 w/ DDR3
16:17imirkin: mwk: what's this "lins" thing?
16:17imirkin: i just need enough to draw transformed points and lines, preferably with color attrib support. dunno if other stuff can affect them.
16:19imirkin: [as an aside, NV10+ have lines...]
16:59mwk: imirkin: NV10 have 3D lines, which work according to different principles
17:00mwk: what do you mean by color attrib support?
17:00imirkin: mwk: yeah, i mean i want GL_LINES
17:00mwk: a "lin" is just a line when the first endpoint is included, the second is excluded
17:00mwk: someone thought that funny, apparently
17:00imirkin: and the coordinates are in raster space? and how are colors assigned?
17:01mwk: it's a 2D primitive, unfortunately
17:01mwk: it works like everything in the 2D engine
17:01imirkin: i see
17:01mwk: coordinates are integers in the pixel space
17:01mwk: as for colors, you only get to choose a single solid color
17:01imirkin: and i assume there's no color interpolation
17:01mwk: subject to the usual 2D rops
17:02imirkin: could i fake it with a tri with 010 or something?
17:02mwk: no, that'd be a 0-area triangle
17:02mwk: not particularly useful
17:02imirkin: yeah =/
17:02mwk: but if you do a bit of a calculation
17:02imirkin: that'd just get culled
17:02mwk: you can render a line as a quad
17:02imirkin: it's not exactly the same, but close enough
17:03mwk: a) figure if it's a horizontal/vertical line, b) add -0.5 and +0.5 to x or y of both endpoints, to end up with 4 vertices
17:04mwk: that should more or less be what GL prescribes anyway
17:04imirkin: yeah, there's funny stuff with the end points
17:04imirkin: with wide lines
17:04mwk: but you won't get anywhere with 2D lins, I'm afraid
17:04mwk: can't you just not support these?
17:04imirkin: well, that's the current situation :)
17:05imirkin: i noticed that lines weren't being rendered
17:05imirkin: and figured i'd look at fixing it
17:05mwk: I mean, don't support line width != 1
17:05imirkin: mmmm... probably
17:05imirkin: there's a max gl line width
17:08imirkin: so basically i have to add 0.5 * viewport width/height to the endpoints
17:08imirkin: 0.5 / viewport width/height
17:09mwk: just 0.5
17:09imirkin: or are all those coords in raster space? i'll ahve to check
17:09mwk: the coordinates you give to NV4 are in raster anyway
17:09imirkin: PUSH_DATAp(push, _tnl_get_vertex(ctx, i), vertex_size);
17:09imirkin: will have to see what that returns
17:10imirkin: of course.
17:10imirkin: return vtx->vertex_buf + nr * vtx->vertex_size;
17:10imirkin: that should have been obvious.
17:11imirkin: yeah i think you're right - it's all raster positions
23:48nullspoon: Quick question. Does anyone here have muxless hybrid working with the newer nvidia cards using nouveau? (notably the 1050 ti)
23:51nullspoon: My system doesn't quite match the steps documented on the optimus page. When I execute xrandr --listproviders, I see my intel, then nothing. When I modprobe nouveau, I see the second provider, but it's name is 'modesetting', not 'nouveau'.
23:54imirkin: nullspoon: shouldn't matter
23:55imirkin: some people have had trouble getting the graph unit in GP107's to come to life in some laptops, but that doesn't sound like it's your issue, at least not based on what you've said so far
23:56nullspoon: Here's another symptom if it helps. I can run lspci and I see my intel as the VGA, and my nvidia as the 3d controller.
23:56nullspoon: If I run lspci after modprobing nouveau though, my system freezes.
23:57nullspoon: I'm a little worried I've got bad hardware.
23:57imirkin: try modprobing nouveau with runpm=0
23:58imirkin: so that it doesn't auto-suspend the gpu
23:58imirkin: running lspci causes a wake-up
23:58nullspoon: ah, thanks. Was googling there. Never see that before. :)
23:59imirkin: here's a more complete list of params: https://nouveau.freedesktop.org/wiki/KernelModuleParameters/
23:59imirkin: not 100% accurate, but what is
23:59nullspoon: True. Well, so far, you're giving me much more than I was able to find in my research.