Could you please compile a version with these debug outputs?
I still can't play doom because i don't know the reason why it hangs at
the start screen. This would really help to solve the problem for me and
mayby some other debian users. :)
Fox Mulder wrote:
I think the debug output would be
I've noticed extremely slow performance while running Doom on FSO M4. I
tracked it down to the accelerometer code. (I turned off accel control in
the opendoom.cfg file and that fixed the speed issue). The code basically
opens /dev/event3 and reads from this. Should I be approaching the
).
Is there anything obvious here regarding the way FSO operates that could
cause this? I'd like to discover the cause and implement a solution quickly.
(Do I need to be on DBUS requesting the resources I need/want?)
Thanks,
SCarlson
--
View this message in context:
http://n2.nabble.com/-FSO--M4--DOOM-Running
I noticed the same, but the solution from another thread worked here -
either execute or put into ~/.profile :
# fix doom accelerators
echo 10 /sys/devices/platform/lis302dl.1/threshold
echo 10 /sys/devices/platform/lis302dl.2/threshold
Stefan
Great tip ! That's why my Doom was so
SCarlson wrote:
I've noticed extremely slow performance while running Doom on FSO M4. I
tracked it down to the accelerometer code. (I turned off accel control in
the opendoom.cfg file and that fixed the speed issue). The code basically
opens /dev/event3 and reads from this. Should I be
://lists.openmoko.org/mailman/listinfo/community
--
This email is a reply to your post @
http://n2.nabble.com/-FSO--M4--DOOM-Running-slow.-tp1493922p1494970.html
You can reply by email or by visting the link above.
--
View this message in context:
http://n2
/SendEmail.jtp?type=nodenode=1494970i=0
http://lists.openmoko.org/mailman/listinfo/community
--
This email is a reply to your post @
http://n2.nabble.com/-FSO--M4--DOOM-Running-slow.-tp1493922p1494970.html
You can reply by email or by visting the link above
7 matches
Mail list logo
