54 replies to this topic

[Ryo]

Nope.
But in the worst case, it could be solved with an option in the configuration panel.

[kevcal]

Well even if it is in open2x (and it will be) it'll still be a daemon . why optimise it? what it does every 5 seconds seems to take about 1500 cycles, and if I'm not making any mistake at 200 MHz that'd be about 7.5 µs. 0.0000075 seconds wasted every 5 seconds, does it sound like it requires optimization? Oh well that's if I compile it with -O2 tho, which I haven't done yet. I'll do it next time. Oh and actually I don't think there'd be much to optimize in assembly anyways, that's the kind of code gcc is great at optimizing. As for memory usage, it doesn't take much more than a hello world, besides a 768 B array...

This is a great accessory.

Heh, the context switch probably takes more time than this does; but I always think code should be as optimised as possible

I personally would prefer not to have a process running in background doing this - why do the values have to keep being re-applied?
Is something else changing them back to the defaults ie what else accesses these registers? If so, can that be disabled or is it a hardware 'feature'?
Note, I have no idea what memregs16[0x295C] points to.

Edited by kevcal, 20 July 2007 - 08:09 AM.

[A_SN]

I personally would prefer not to have a process running in background doing this - why do the values have to keep being re-applied?
Is something else changing them back to the defaults ie what else accesses these registers? If so, can that be disabled or is it a hardware 'feature'?
Note, I have no idea what memregs16[0x295C] points to.

gmenu2x and gpfce change these values, and some others probably do too, so if you run these it ruins the fix, that's why it keeps being re-applied. I could make a check to see if things have been changed instead of systematically writing over and over again, but that wouldn't be much more efficient, would it?

[kevcal]

Fair enough - yeah wasn't advocating that - just wondered why it needed to keep 'doing it'.
Looking at this stuff makes me realise I ought to digest the MP2520F(?) databook.

[fusion_power]

It seems a lot of users find this useful, so I could actually look into integrating it in gmenu2x if there is demand for such a feature.
I have a MKI though and I am happy with it so I wouldn't directly benefit from this
I would also have to look into having this coexist with the gamma settings (or removing them)

Yes, I think it would fit nicely in Gmenu2X. Because the MKII Fix is not in every app useful, a per game enabling/disabling would be the best. The Colour Correction option should be put in the Link settings.

[mfk]

I use an MK2 and I found this little application very usefull. I can't play any games without it.

[Cruel]

Thanks! Its much better now, especially in dark games.
Cool thing, i wonder if i can insert this in autorun somehow?

[A_SN]

Thanks! Its much better now, especially in dark games.
Cool thing, i wonder if i can insert this in autorun somehow?

Of course, just call it from an autorun script.

Edited by A_SN, 07 August 2007 - 03:47 PM.

[Dunny]

Thanks! Its much better now, especially in dark games.
Cool thing, i wonder if i can insert this in autorun somehow?

Of course, just call it from an autorun script.

Not working here. If I run the autorun.gpu from the menu, it runs just fine. Unfortunately, it doesn't run on startup - and yes, I do have autorun enabled and the script is named correctly, and is in the root of the SD card

D.

[A_SN]

Thanks! Its much better now, especially in dark games.
Cool thing, i wonder if i can insert this in autorun somehow?

Of course, just call it from an autorun script.

Not working here. If I run the autorun.gpu from the menu, it runs just fine. Unfortunately, it doesn't run on startup - and yes, I do have autorun enabled and the script is named correctly, and is in the root of the SD card

D.

Well, well I'll release officially a finished version of it, it'll come with an installing script which will add some command for it to run somewhere in some file in /etc, so no autorun will be involved.

EDIT : It has been brought to my attention that you can do such a thing by editing /root/startup.sh

Edited by A_SN, 09 August 2007 - 05:51 PM.