[Mod ObScUrE]

1. Going back to Main Menu is now fixed.
2. Raw Mouse Buttons works fine on very fast Beretta spamming.
3. Performance decreased heavily (tested both vanilla renderer Default & Old Cpu build) now I get big fps drops and I had to adjust s_mixprestep from 0 to 0.05 before it worked without distortion.
(tested with dmaEX_EffectsEnable 1 and 0 on 22050Hz)

This post has been edited by ObScUrE: 17 July 2010 - 04:53 PM

[p5yc0runn3r]

s_

ObScUrE, on 17 July 2010 - 03:11 PM, said:

1. Going back to Main Menu is now fixed.
2. Raw Mouse Buttons works fine on very fast Beretta spamming.
3. Performance decreased heavily (tested both vanilla renderer Default & Old Cpu build) now I get big fps drops and I had to adjust s_mixprestep from 0 to 0.5 before it worked without distortion.
(tested with dmaEX_EffectsEnable 1 and 0 on 22050Hz)

s_mixahead should be 0.1
s_mixprestep should not be 0.5 but 0.05

[Mod ObScUrE]

Typo don't worry about it p5yc0runn3r. :-)

This post has been edited by ObScUrE: 17 July 2010 - 07:46 PM

[mitsubishi]

After great help by p5yc0runn3r (I've no much idea about s_ stuff), files are updated with better defaults for dmaEX: com_soundmegs defaults to 32, if it's below 16 (in many old configs) it sets it to 16.

Additionally, an internal dmaEX sanity check involving mixahead and prestep is adjusted.

--

potential glitch on mouse keys detected; keys may be repeating wrongly in certain conditions, investigating.

--

potential glitch identified. testing and uploading incoming. apparently keypresses must be remembered if they come too fast for the game


--

repetition glitch persists; investigating. closer now; it appears to occur when 2 keys are pressed simultaneously. their 'up' event may be lost. hm..

--

aha! solution.

This post has been edited by mitsubishi: 17 July 2010 - 08:21 PM

[mitsubishi]

ok, Mouse Buttons on Raw Mode are fixed again.

Now using a more direct method; it should be lower latency and it avoids quirks I had noticed.

--

The "Com_QueueEvent overflow" spam sometimes is a normal nuisance due to the simplistic implementation that I will avoid in a later update.

This post has been edited by mitsubishi: 17 July 2010 - 09:05 PM

[Mod ObScUrE]

Original ioUrT can handle s_mixprestep 0 so it's better optimized currently?
Before the 'go back to MainMenu' issue was fixed it worked flawless on s_mixprestep 0
so is there a way to get the performance back or improve it on another way on my system it's a huge difference.

-
newest build has an issue with Mouse4 and Mouse5 button.

Mouse4 works
but mouse5 executes the action from mouse4 and not that what was bound to mouse5.

This post has been edited by ObScUrE: 17 July 2010 - 09:19 PM

[mitsubishi]

^fixed.

only the 170710-6 files may work properly now, and that if, i'll fix later.

This post has been edited by mitsubishi: 17 July 2010 - 09:30 PM

[Mod ObScUrE]

There is a difference from MainMenu to game sound.
The MainMenu seems to run with 44100Hz I get the distortion there but ingame it works without distortion on s_mixprestep 0

Oh you changed the default value on s_sdlspeed 0 [from 22050 to 44100].
I was thinking you had set a default value for s_sdlspeed to 44100 :-)
-
It works all perfect now and raw mouse input does a well job.

This post has been edited by ObScUrE: 18 July 2010 - 02:32 AM

[mitsubishi]

Yes, it does appear ok (on the "170710-6" builds). Now to avoid a flooding of event queue..

This post has been edited by mitsubishi: 18 July 2010 - 09:03 AM

[~SG~Juno]

So i used both 170710 .exes
Its much better.
But there is still random stop shooting. Its better cause its not so often. Now i can play on public servers... definitely not CW/PCW.
And steel i feel something like lower firing rate which is almost on edge of perception. Im not sure if ita exists, but feel like it is.