Black Screen with Moonlight

[rob]

Hi guys, thanks for this great project. Almost everything works out of the box. Really cool!!

Today i have upgraded my system to Version 4.00 beta 5 and i'm trying to get moonlight to work.

Pairing and scraping works without any problem. When i start steam with moonlight i get a black screen on the tv. The Computer is switching to big picture mode and i can control the pc with my recalbox controler. Sound works also over the tv, just the tv remains black.

Any ideas?

Regards, rob

[Substring]

Hey @rob !

You're running GFE 3.0.7right ? so 2 choices remain :

• either switch to the unstable branch
• either wait for the next release

[rob]

Thanks for the quick reply. I will try another version later.

Cheers

[rob]

It works with GFE 2.2.2, thank you!!

Now i have a little problem with my PS3 controller. The horizontal axis from the right analog stick doesn't work, only with moonlight... Vertical axis works perfect.

I have remapped the pad in emulation station and i also tried the mapping in moonlight with ./moonlight.sh map. The stick works in the mapping tool and also in other emulators like n64...

[Substring]

mmmhhh could you paste the content of ~/configs/moonlight/mappingP1.conf ?

[rob]

# Device name = PLAYSTATION(R)3 Controller
# SDL2 GUID   = 060000004c0500006802000000010000
# Event path  = /dev/input/event2
btn_west = 300
btn_tl2 = 296
btn_dpad_left = 295
reverse_dpad_y = false
reverse_dpad_x = false
btn_dpad_down = 294
btn_dpad_up = 292
abs_ry = 3
abs_deadzone = 4
btn_south = 301
btn_start = 291
btn_dpad_right = 293
reverse_ry = true
reverse_rx = false
btn_mode = 304
abs_x = 0
abs_y = 1
btn_tr2 = 297
reverse_x = false
reverse_y = true
btn_thumbl = 289
btn_east = 302
btn_select = 288
btn_tr = 299
btn_north = 303
btn_tl = 298
btn_thumbr = 290

and if needed the es_input.cfg

	<inputConfig type="joystick" deviceName="PLAYSTATION(R)3 Controller" deviceGUID="060000004c0500006802000000010000">
		<input name="a" type="button" id="13" value="1" code="301" />
		<input name="b" type="button" id="14" value="1" code="302" />
		<input name="down" type="button" id="6" value="1" code="294" />
		<input name="hotkey" type="button" id="16" value="1" code="304" />
		<input name="joystick1left" type="axis" id="0" value="-1" code="0" />
		<input name="joystick1up" type="axis" id="1" value="-1" code="1" />
		<input name="joystick2left" type="axis" id="2" value="-1" code="2" />
		<input name="joystick2up" type="axis" id="3" value="-1" code="3" />
		<input name="l2" type="button" id="8" value="1" code="296" />
		<input name="l3" type="button" id="1" value="1" code="289" />
		<input name="left" type="button" id="7" value="1" code="295" />
		<input name="pagedown" type="button" id="11" value="1" code="299" />
		<input name="pageup" type="button" id="10" value="1" code="298" />
		<input name="r2" type="button" id="9" value="1" code="297" />
		<input name="r3" type="button" id="2" value="1" code="290" />
		<input name="right" type="button" id="5" value="1" code="293" />
		<input name="select" type="button" id="0" value="1" code="288" />
		<input name="start" type="button" id="3" value="1" code="291" />
		<input name="up" type="button" id="4" value="1" code="292" />
		<input name="x" type="button" id="12" value="1" code="300" />
		<input name="y" type="button" id="15" value="1" code="303" />
	</inputConfig>

[Substring]

yeah, a typo that i solved (cuz i'm the one responsible for it) a few weeks ago https://github.com/recalbox/recalbox-configgen/commit/0e88ab998ad2dacf86e3138e2c3c0522fc474394

once again : either switch to the unstable, either wait for the next release

in fact, you can even solve it yourself if you have a few basc skills in linux

[rob]

@subs

Thanks again. I fixed it with a new mappingP1.conf

this works perfect...

abs_x = 0
abs_y = 1
abs_z = 50
abs_rx = 2
abs_ry = 3
abs_rz = 51
abs_deadzone = 4
abs_dpad_x = 0
abs_dpad_y = 0
reverse_x = false
reverse_y = true
reverse_rx = false
reverse_ry = true
reverse_dpad_x = false
reverse_dpad_y = false
btn_west = 303
btn_south = 302
btn_north = 300
btn_east = 301
btn_select = 288
btn_start = 291
btn_mode = 304
btn_thumbl = 289
btn_thumbr = 290
btn_tl = 298
btn_tr = 299
btn_tl2 = 296
btn_tr2 = 297
btn_dpad_up = 292
btn_dpad_down = 294
btn_dpad_left = 295
btn_dpad_right = 293

[Substring]

@rob yeah, can be done that way. But if you ever bring in another pad, it can be messed up. But you understood how t fix it anyway for ypur needs