Homebrew RetroArch - A new multi-system emulator

[LibretroRetroArc]

AGAIN!!! the TV argument OVER AND OVER AND OVER....
What part of my post didn't you understand? I'm not denying input lag, I'm telling you that THERE'S MORE LAG WITH A CC CONTROLLER!!
MORE LAG, MORE MORE. Do you understand?

If all the problem you have is this:

TV    TVLAG  CCLAG  I.LAG
CRT =  0ms    30ms =  30ms  (not noticeable, but the issue is still there)
HDTV=  20ms  30ms =  50ms  (noticeable)

Just saying that if I was with a CRT I wouldn't notice (and hence is not worth to care because I'm with a HDTV), it doesn't deny that there is still an underlying issue with the CC controller.
AGAIN I tell you, do you know bittrip runner?, I will never play such a reaction demanding game ever, it was with my wii, composite connection, wiiremote, finished it without major control problems. I don't need more. (and I repeat, composite connection, deinterlacing, rescaling, PP on, and on my HDTV, all the crap you named, not enough to notice input lag, all I needed was retroarch and a CC controller)

"Go ahead and read this entire article"
About all the TV babbling, you are just showing how little you read the forum. Let me point me to the post where I tell the res of my screen. Please, go ahead and read my entire post.
And for the nth time, read my original post, please. Don't start talking about interlacing and crap. I use component, you know what that means? yes, progressive. For the rest of the lecture, again, my original post.

"has no right to complain"
Now you start talking about rights, you are in total denial man. Please refer to my above explanation, you are just forcing people to not notice the issue by using a CRT.

I'm growing really tired of you now - it's pretty obvious that talking to you is like talking to a brick wall. You can't even get your facts straight and you misrepresent whatever I try to say to you and try to spin it off into something else because it seems you no longer want to come out that you are using a 2006 HDTV since you know what the repercussions of you admitting that would be.

So let me get this straight once more since you never bothered to confirm (and likely won't) - you're using a 2006 HDTV, right? (which means it's a total piece of crap) And you want to talk to me about 'lag' and getting all uppity about it? That's just hilarious.

Anyways, take it up with the libogc devs if this affects every piece of homebrew - once again, not my problem. Oh BTW, one piece of advice - when you go and talk to them, don't act all 'entitled' like you did to me or chances are they'll tell you to go do something to yourself in a rather unsavory way. Try to be civilised and humble, especially when you yourself are bringing nothing to the table.

 

[quepaso]

I think the problem is from libogc or whatever its called, these guys are having lag issues in HBC and other apps outside of retroarch with the CC pro, so its likely an issue there. So there is 0 reason to bother retroarch about it. Talk to the guys who did the original code. If libretro does a compile using the nintendo SDK, im sure that would ease everyones concerns since its likely it will work flawlessly in that environment.

 

[LibretroRetroArc]

I think the problem is from libogc or whatever its called, these guys are having lag issues in HBC and other apps outside of retroarch with the CC pro, so its likely an issue there. So there is 0 reason to bother retroarch about it. Talk to the guys who did the original code. If libretro does a compile using the nintendo SDK, im sure that would ease everyones concerns since its likely it will work flawlessly in that environment.

Yep, and I even told this Dogway guy earlier that I'm open to exploring if a Revolution SDK build can be done - but that won't stop him bitching you see.

Probably there never were any 'high-reaction games' he could play in the past on his Wii so the dude is only now noticing his TV for the utter piece of crap it is today. No, 3rd Strike demo running tolerably on 360 doesn't mean a damn thing since those games/ports are butchered like hell to run 'tolerably' on every HDTV ranging from the shitty low-end (2006 ) to tolerable (2012) today - and the reason they do that is because they don't like a person with entitlement issues harrassing them with 'INTOLERABLE LAG' complaints - that, and the 360 is probably outputting in your HDTV's native res so that helps a lot since it doesn't have to rescale.

 

[CobraStr1ke]

Guys sorry you have to deal with all this ^ It sounds like hes using a piece of shit TV sorry to say it. Try it out on a new television form lets sayyyy maybe 2011 and up and see if you still have an issue. See if you can get access to a Panasonic Plasma if a friend has one. Or better yet go get a CRT on Craigslist and play them the way they were meant. I scooped up a sick ass Samsung virtually brand new CRT for $15 (=

......Anyways guys I asked last night but I see this topic got derailed. I have my Wii hooked up through component (official RGB Wii cables) to my CRT, I posted some quick pics last night of what my Yoshis Island looks like....is this the optimal settings to show scanlines etc etc or is there even a better way. Ill break it down, NTSC Wii, RGB cables on a CRT that I believe does 480i tops although I can be wrong about that and maybe it does 480p. Either way I have point filtering on and was wondering if anyone can assure me this is the way I should go with the whole set-up before I start gaming on it. Thanks again!

 

[LibretroRetroArc]

Guys sorry you have to deal with all this ^ It sounds like hes using a piece of shit TV sorry to say it. Try it out on a new television form lets sayyyy maybe 2011 and up and see if you still have an issue. See if you can get access to a Panasonic Plasma if a friend has one. Or better yet go get a CRT on Craigslist and play them the way they were meant. I scooped up a sick ass Samsung virtually brand new CRT for $15 (=

......Anyways guys I asked last night but I see this topic got derailed. I have my Wii hooked up through component (official RGB Wii cables) to my CRT, I posted some quick pics last night of what my Yoshis Island looks like....is this the optimal settings to show scanlines etc etc or is there even a better way. Ill break it down, NTSC Wii, RGB cables on a CRT that I believe does 480i tops although I can be wrong about that and maybe it does 480p. Either way I have point filtering on and was wondering if anyone can assure me this is the way I should go with the whole set-up before I start gaming on it. Thanks again!

Sounds good enough to me.

 

[CobraStr1ke]

Sounds good enough to me.

Ok thanks bud. I just wanted to make sure I dont need some type of scanline box or something of that nature. I also see people asking for the emulator forcing 240p? I was just curious if I am running this essentially in 480i? Im playing Yoshis Island and it appears as if I see scanlines but it almost seems like they are running from top to bottom vertically, instead of across the screen horizontally.

Also Lib....I do want to use these component cables for SNES etc off the wii and not the standard red, white , and yellow correct?
Finally is there any visual advantage or any advantage besides save states to running this emulator for SNES as opposed to using VC Wads? One huge advantage so far for me is that Yoshis Island is not injectable into a WAD as far as I know as well as Secret of Mana 2 English translated version. Just curious if the VC games look just as good as this emulator without point filtering....

Thank you again for the technical questions I have.

 

[LibretroRetroArc]

I'm into the technical side of digital video and imagery, and so forth I know these things because I learned them. I wouldn't be surprised if the algorithm was a simple bicubic. Again, you are just making stupid questions, because all that matters is the LAG DIFFERENCE BETWEEN CONTROLLERS, ignore the fucking TV, and face the facts.

Face what facts? That there is a technical problem with libogc possibly in conjunction with wireless expansion controllers and that there's nothing I can do about it, and that its effects are most pronounced on shitty HDTVs from 2006?

BTW - I told you this a bunch of times now.

BTW2 - you're into the 'technical side of imagery and digital video', yet you don't have a clue that a HDTV from 2006 is a total crapfest and that you don't have a right to complain when it comes to input lag? Do you even have a clue how low/high your response time is on this TV?

Why do you want to blame RetroArch for a problem that is most likely caused by your TV first and foremost, and then possibly libogc as a very distant second? Why do you expect me to 'care' about a problem that is caused by noone other than you for buying the damn thing in the first place? Even your TV manufacturer doesn't give a damn that they sold you this thing - so why should I? Go call up Samsung consumer support and see how long you last - they will spend less than 1/3th of the time on you than I am wasting on you right now.

BTW3 - Any dev that has to 'listen' to a guy like you being this abrasive and this offensive would immediately tell you to go 'F' yourself - I hope you realize that - you probably think this is the way to go about it, but I can tell you it's not. To be honest, I'm surprised you haven't been banned yet - this must not have been the first time you have had these kind of psychotic episodes.

 

[CobraStr1ke]

LibretroRetroArc I just tested Mednafan and I set Sonic the Hedgehog to 240p through the double-strike setting in the option. I must say I can now clearly see the scanlines. I then used retroarch and it is as I suspected, it looks great dont get me wrong but the scanlines are like non existant on my CRT. Is there any chance you will have 240p mode implemented into RetroArc? Would it be difficult to do so? I also noticed someone else asking if it would ever have forced 240p mode a couple pages back. Please let me know and also I must say the difference is very noticeable to me.

 

[LibretroRetroArc]

LibretroRetroArc I just tested Mednafan and I set Sonic the Hedgehog to 240p through the double-strike setting in the option. I must say I can now clearly see the scanlines. I then used retroarch and it is as I suspected, it looks great dont get me wrong but the scanlines are like non existant on my CRT. Is there any chance you will have 240p mode implemented into RetroArc? Would it be difficult to do so? I also noticed someone else asking if it would ever have forced 240p mode a couple pages back. Please let me know and also I must say the difference is very noticeable to me.

Double strike mode is already implemented - ToadKing posted some beta versions earlier but you should probably wait for RetroArch 0.9.8 since those beta versions were a bit unstable. RetroArch 0.9.7 didn't have the double strike modes yet.

 

[CobraStr1ke]

Double strike mode is already implemented - ToadKing posted some beta versions earlier but you should probably wait for RetroArch 0.9.8 since those beta versions were a bit unstable. RetroArch 0.9.7 didn't have the double strike modes yet.

Oh thank you sir thats great news!!! I totally almost shit bricks when I saw the scanlines and what Im supposed to be seeing. Your emu is dope bro. You guys are doing a great job! Any chance if you can point me to where the ones he posted are as I just want to test some SNES to compare to what I have now? Also I take it a regular Virtual Console game would not have scanlines, 240p, implemented? Which would make this even more the reason to use especially for a CRT. Thanks again bud!

Also I am excited for the new one you guys will drop with the 240p in it!

I skimmed through all the pages and read him mentioning to compile it around page 33. I havnt tried it yet but if anyone has the beta RetroArch emu with 240p implemented please let me know!

 

[Dogway]

Face what facts? That there is a technical problem with libogc possibly in conjunction with wireless expansion controllers and that there's nothing I can do about it, and that its effects are most pronounced on shitty HDTVs from 2006?

holy shit, finally admitted (keep reading on my @BTW reply)

"Anyways dude, what was your problem again with the Dutch?"

That's my question, back in August, remember? Your hostile attitude to my simple and straight bug reports. Ton of them, no feedback. Then one thing: *rolls eyes*

@BTW: you run into contradictions everytime you claim that by yourself and then denies my speech because I own an old TV.

@BTW2: and precisely because I am on the 'technical side of imagery and digital video' I can tell you that most HDTV's are mostly the same. And only differ on the LCD (backlight, etc) specs and PP. The chipset is mostly always the same which is what handles the scaling, deinterlacing, IVTC, etc and hence the load of the LAG concept. So saying that a TV is from 2006 has no real meaning unless what you compare are chipsets.

The foremost problem with you is that you (again, so tired excuse ain't it?) assume that I'm complaining about input lag with my TV, and that's wrong. My main concern is the LAG DIFFERENCE with a CC Pro over the GC controller, whether I'm checking on my samsung, a LG, a Hitachi, a Sony Bravia, my cell phone, a custom made craft screen or your godly CRT. You are so thick that you can't even get past this concept.

 

[Vague Rant]

As has been explained to you repeatedly, if the problem is with libogc, it's irrelevant to this thread. We don't need multiple pages of you ranting about it either, because it simply doesn't appear to be a RetroArch issue.

 

[LibretroRetroArc]

Face what facts? That there is a technical problem with libogc possibly in conjunction with wireless expansion controllers and that there's nothing I can do about it, and that its effects are most pronounced on shitty HDTVs from 2006?

holy shit, finally admitted (keep reading on my @BTW reply)

"Anyways dude, what was your problem again with the Dutch?"

That's my question, back in August, remember? Your hostile attitude to my simple and straight bug reports. Ton of them, no feedback. Then one thing: *rolls eyes*

@BTW: you run into contradictions everytime you claim that by yourself and then denies my speech because I own an old TV.

@BTW2: and precisely because I am on the 'technical side of imagery and digital video' I can tell you that most HDTV's are mostly the same. And only differ on the LCD (backlight, etc) specs and PP. The chipset is mostly always the same which is what handles the scaling, deinterlacing, IVTC, etc and hence the load of the LAG concept. So saying that a TV is from 2006 has no real meaning unless what you compare are chipsets.

The foremost problem with you is that you (again, so tired excuse ain't it?) assume that I'm complaining about input lag with my TV, and that's wrong. My main concern is the LAG DIFFERENCE with a CC Pro over the GC controller, whether I'm checking on my samsung, a LG, a Hitachi, a Sony Bravia, my cell phone, a custom made craft screen or your godly CRT. You are so thick that you can't even get past this concept.

Right - you're on the 'technical side of imagery and digital video' because you took somebody else's AV script and 'improved' on it, and then posted it on Doom9. I'm impressed. I'm also impressed that you informed us that a chipset is doing the scaling inside a TV - it's about as informative to me as being aware that a CPU is in care of central processing inside a computer.

I'm just going to ignore your posts from now on if you don't mind unless they have some much-needed substance to them (good luck with that). Stir up any more 'fights' and I'll just report your subsequent posts for harrassment, derailment and fight stirring. I have no time for this nor any need to engage in it anymore. Perhaps you like to waste your time (I assume you have lots of it to waste no doubt), but my time is valuable to me - and what you're doing right now is worse than stealing my money - you're wasting my time - my most valuable asset - you can get your money back but I can never get my time back, and I can be doing lots of other productive things with my time that is now being wasted on this fruitless argument.

So bye bye and so long - your opinion has been duly noted, time to move on now.

 

[Toad King]

Wow, this is a lot of posts of people complaining and not a lot of posts of this:

I will be willing to go out of my way and look more into these issues if the people reporting them can do the following things:

* Only use official Wiimotes and Classic Controllers. No ebay/dealextreme crap.
* Can test it on a CRT display. No LCD/Plasma/whatever.
* Can confirm it only has issues with RetroArch, not any other homebrew apps (HOMEBREW, NOT ACTUAL WII GAMES/WIIWARE/VIRTUAL CONSOLE).
* Get a video of it.

If you can do these things, then I will try to look into it. Otherwise, it's not worth the time searching it down since so many things could be the cause.

 

[CobraStr1ke]

Wow, this is a lot of posts of people complaining and not a lot of posts of this:

Hey Toad King thanks for your contribution to this awesome emu. I am waiting until 240p is implemented as Lib said its in the next update but he mentioned that you made some beta of the emu with it. Any chance you can point me in the right direction of where it is? Thanks, also on a sidenote im using Mednafan in the meantime to test in 240p and it looks gorgeous off my CRT, little to no flicker and scanline heaven (= ---> I would love to try your beta version on SNES. Thanks in advance! You guys rock!

 

[Toad King]

Hey Toad King thanks for your contribution to this awesome emu. I am waiting until 240p is implemented as Lib said its in the next update but he mentioned that you made some beta of the emu with it. Any chance you can point me in the right direction of where it is? Thanks, also on a sidenote im using Mednafan in the meantime to test in 240p and it looks gorgeous off my CRT, little to no flicker and scanline heaven (= ---> I would love to try your beta version on SNES. Thanks in advance! You guys rock!

We don't release betas to the public, we mainly just use the monikers internally for testing. If you want to try it yourself you'll have to compile it from the repo.

EDIT: I posted a version of the Snex9x core a while back with it I think, but I would have to go back and find it and I found some issues with it that have been fixed since.

 

[CobraStr1ke]

We don't release betas to the public, we mainly just use the monikers internally for testing. If you want to try it yourself you'll have to compile it from the repo.

EDIT: I posted a version of the Snex9x core a while back with it I think, but I would have to go back and find it and I found some issues with it that have been fixed since.

Ok no worries. I saw its a couple simple steps I guess to compile it so maybe I will try it out later when I get the chance to look. Thank you and I may just stick with the Genesis in 240p for now and wait till the next big update, thanks !

 

[Dogway]

"Right - you're on the 'technical side of imagery and digital video' because you took somebody else's AV script and 'improved' on it, and then posted it on Doom9. I'm impressed. I'm also impressed that you informed us that a chipset is doing the scaling inside a TV - it's about as informative to me as being aware that a CPU is in care of central processing inside a computer."

Back to trolling? I don't post over Doom9, my link leads to Doom10. And if I said "improvement" is because I'm not as arrogant as you (95% is from scratch, besides different scripts), or you are gonna tell me now that you are not borrowing someone else's work for your retroarc? are you kidding man?

And you don't know anything about TV's, if you dismiss the fact that TV chipset cycles are not like CPU cycles nor TV brand cycles, you are trolling as f!*/$. One TV chipset can share an array of TV brands and models through the span of the years, you can count the total amount of chipsets with your hands fingers, is not like there are ton of them. It's the same as Optical Drive Chipsets and so on, it's only that you are an ignorant troll who pretends to know it all. Whoever comes here can clearly see how you circumvented all the direct questions I made to you, while I answered all of them you made to me. You are only worried to reply to the "stir up" answers instead of staying on-topic.

 

[LibretroRetroArc]

To any moderators: I've told this guy now dozens of times to call it quits and answered most of his actual 'questions' in a more or less nice fashion (even when the situation didn't call for it as he was insulting me numerous times), but he just doesn't call it quits - can we please get this rubbish off the main thread? His rants aren't even about RetroArch anymore - it's just plain trolling, harrassment and spam - two/three pages about nothing.

If he has a personal issue with me, keep it to PM - but he should keep this rubbish off the main thread.

Thanks.

 

[Toad King]

"Right - you're on the 'technical side of imagery and digital video' because you took somebody else's AV script and 'improved' on it, and then posted it on Doom9. I'm impressed. I'm also impressed that you informed us that a chipset is doing the scaling inside a TV - it's about as informative to me as being aware that a CPU is in care of central processing inside a computer."

Back to trolling? I don't post over Doom9, my link leads to Doom10. And if I said "improvement" is because I'm not as arrogant as you (95% is from scratch, besides different scripts), or you are gonna tell me now that you are not borrowing someone else's work for your retroarc? are you kidding man?

And you don't know anything about TV's, if you dismiss the fact that TV chipset cycles are not like CPU cycles nor TV brand cycles, you are trolling as f!*/$. One TV chipset can share an array of TV brands and models through the span of the years, you can count the total amount of chipsets with your hands fingers, is not like there are ton of them. It's the same as Optical Drive Chipsets and so on, it's only that you are an ignorant troll who pretends to know it all. Whoever comes here can clearly see how you circumvented all the direct questions I made to you, while I answered all of them you made to me. You are only worried to reply to the "stir up" answers instead of staying on-topic.

Please follow the steps in this post if you're going to keep posting about your input lag issues.