you meannouseforname wrote:... by changing the "update" time in config this happend much less already.
ok i'l try variable these settings.<updateinterval>15</updateinterval>
you meannouseforname wrote:... by changing the "update" time in config this happend much less already.
ok i'l try variable these settings.<updateinterval>15</updateinterval>
lyova wrote:you meannouseforname wrote:... by changing the "update" time in config this happend much less already.ok i'l try variable these settings.<updateinterval>15</updateinterval>
Oh, so what you mean is that it actually crashes in the moment when the hpm mode should kick in?lyova wrote: yes... and if in game more when 35 users online
and i'm run xaseco I have always this error
Code: Select all
<show_min_recs>5</show_min_recs>
<!-- Display existing records at start of a new track? -->
<!-- 2 = in message window, 1 = in chat, 0 = none -->
<show_recs_before>0</show_recs_before>
<!-- Display (possibly) updated records at end of a track? -->
<!-- 2 = in message window, 1 = in chat, 0 = none -->
<show_recs_after>0</show_recs_after>
<!-- Display records range if there are no new records? -->
<show_recs_range>False</show_recs_range>
<!-- Do you want XASECO to display newly driven records? -->
<display_recs>False</display_recs>
So lille79, <display_recs> needs to stay True.Lovemaster wrote:A little off the current topic... Is it possible to display the Dedimania recs only in the widget, while still showing newly driven recs in chat? Seems if I opt to not display recs in chat, the widget stops working as well. Using the latest versions of both Xaseco and Fufi Widgets.
Of course the problem may also be with an unresponsive Dedimania connection, which has been VERY frequent as of late... So if I leave "show recs before AND after" disabled and leave "show recs" true, would that be the proper setup?f*ckfish wrote:Nope, Xymph just meant, that Lovemaster wanted to still display the new records inside the chat, so he needs "true" for that option.
The dedimania widget will work as long as the dedimania plugin keeps on updating the dedi_db variable onPlayerFinish. Don't know when exactly this won't be the case anymore but obviously Lovemaster found a way to do so
Code: Select all
<!-- Display existing records at start of a new track? -->
<!-- 2 = in message window, 1 = in chat, 0 = none -->
<show_recs_before>0</show_recs_before>
<!-- Display (possibly) updated records at end of a track? -->
<!-- 2 = in message window, 1 = in chat, 0 = none -->
<show_recs_after>0</show_recs_after>
<!-- Display records range if there are no new records? -->
<show_recs_range>False</show_recs_range>
<!-- Do you want XASECO to display newly driven records? -->
<display_recs>True</display_recs>
Huh? I almost never see Dedimania connection problems in my server logs anymore, and nobody else has mentioned it in these forums for a while either. Got a flaky connection yourself perhaps?Lovemaster wrote:Of course the problem may also be with an unresponsive Dedimania connection, which has been VERY frequent as of late...
Thx guys, that's what I'm after.. I did have it set right, must've been a problem with the dedimania conx itself. To answer your question Xymph, it's running on a 100Mbps UNIX webserver, so maybe I need to double-check my settings. It connects to Dedimania about half the time.lille79 wrote:Sorry for confusing you. As Xymph correctly understood, this is your correct setting:This is if you don't want records before and after a track, but wants to show in the chat when a new record-time is set.Code: Select all
<!-- Display existing records at start of a new track? --> <!-- 2 = in message window, 1 = in chat, 0 = none --> <show_recs_before>0</show_recs_before> <!-- Display (possibly) updated records at end of a track? --> <!-- 2 = in message window, 1 = in chat, 0 = none --> <show_recs_after>0</show_recs_after> <!-- Display records range if there are no new records? --> <show_recs_range>False</show_recs_range> <!-- Do you want XASECO to display newly driven records? --> <display_recs>True</display_recs>