ok, i was playing SA2 in dark story in wire frame, i was robotnik when he firsts start the pyramid lvl and i thought maybe i'll be able to see something so i took it off and i DID, i played a nice chunk like it was normal but when i went near an enclosed space or near a wall where the camera is goin through tat wall i get the same graphics problem so its not the graphics, ITS THE CAMERA!!!!!!!!!!, now only if i were a coder or modder or anyone who could patch this i'd do it, since its a camera problem i don't think theres a problekm with the emu its the camera, try it for yourself, the pyramid lvl with robotnik:bouncy:
I think i know why sonic Adventure 2 does wat it does
- Thread starter Ultima226
- Start date
General Plot
Britchie Crazy
Wow, and I thought the emulator's authors had thought of everything, that is, until the idea that the crash may be due to the camera and not the graphics. Oh wait, as it turns out, it is the graphics that causes the crash. Please understand one thing: many games have the gfx/text bug. THPS2 is a good example, and there is really no "camera" to control in that game. It is a graphics bug, no matter how you may interpret it. These guys are geniuses, please understand that they have considered even the most obvious. Also, 'cameras" have never been an issue in emulators, and I doubt it will start here. 
Last edited:
General Plot
Britchie Crazy
The bug is graphics related, not "camera" related. The authors have already stated that it is an iterpretation of the graphics that causes this. Do some research further back in the forums, and you can see this for yourself. If you still disagree, then perhaps you can diagnose and debug the error, but I'm willing to guess that you don't know the first thing about how this emu even begins to work, so please leave it to the professionals.
General Plot
Britchie Crazy
It may not be nice, but it is true. I was nicer with my first post telling him that this was a graphics bug confirmed by the original developers of Chankast, and I defy anyone to tell them that they don't know what they are talking about. Camera controls and points of view aren't the problem, the graphcis being interpreted incorrectly is. Perhaps you'd be best to also do a little research. I've been following this project for quite some time (even before I registered with emutalk) and I have seen the bug reports posted.GCFreak said:
General Plot
Britchie Crazy
This points out nothing and pictures will prove nothing. Bug reporting is only helpful if the origin of the bug is known and reported. But if you wish to keep yourself in the dark, then I guess you would rather not know this.Ultima226 said:
generalplot said:
Holy crap and who made you god? No one, so please stop being more of a troll than a knowledgeable poster. I would however like to mention that as a CAMERA moves back and fourth it does move the graphics and works with them, so it's still a graphics problem.
To the topic author: However, that's a nice trick you figured out, thanks a lot for it.
I might try it some time. By the way, it could maybe be a memory problem with too many pixels on the screen or with large images... I would like to mention to the semi-troller one thing:
A program requires a lot of typing, a lot of coding. The devs could miss something, it isn't unheard of. However, we all like what they've done with the emulator, and they really don't need to work their butts off to get it done, they can take their time so missing things is alright.
Last edited:
General Plot
Britchie Crazy
Let me tell you something, lil n00b, and I'll be nice the first time. The gfx may be rotated/zoomed and such by camera control, but that does not mean the camera is graphics related. The camera is controlled by the game pad plugin, the graphics are controlled by the graphics plugin. In each case these plugins are embedded in the emulator. But a bug in the graphics plugin does NOT mean the gamepad plugin has a bug. They are not the same thing. It may APPEAR that the camera would cause errors, but it is in fact the graphics only. Take a look at Tony Hawk's Pro Skater 2 if you don't think I'm right. There's no camera to control in that game whatsoever, and yet, the text graphics bug shows up. Next time, do your homework before you come in here talking like that, when you don't even understand the basic concept of an emulator.Talikar said:
Wow I never said anything about a gamepad did I? I believe I also mentioned the camera is in essence part of the graphics, so, in essense it could be graphics related, but it could also be memory related. I never said anything about game pad, try re-reading my post before you claim I'm a noob and continue your trolls.
Or maybe I wasn't clear so I'll say again:
It could be a memory or a camera related problem, camera is related to graphics since it controls which GRAPHICS you look at/see at the time. So lil noob 12 year old (sorry have to resort to your level) try getting the broom out of your behind for 5 seconds.
Besides, if you re-read my first part of my post you'd notice I semi-agreed with you so what's your problem?
Or maybe I wasn't clear so I'll say again:
It could be a memory or a camera related problem, camera is related to graphics since it controls which GRAPHICS you look at/see at the time. So lil noob 12 year old (sorry have to resort to your level) try getting the broom out of your behind for 5 seconds.
Besides, if you re-read my first part of my post you'd notice I semi-agreed with you so what's your problem?
General Plot
Britchie Crazy
I'm not going to sit here and argue with you. I have an idea: get on irc, and ask one of the devs about this theory of yours. I can assure you that they will laugh at you. The camera may manipulate what is being shown on screen, but in no way does it effect what the gfx plugin is doing, other than to change perspective, which is not going to cause a bug. The misinterpreted graphics solely in themselves are a bug. Plain and simple.
Last edited:
Again I say I semi-agreed with you, but if you don't want to argue with "yourself" that's uh fine with everyone on the board, thanks. oO
Anyway, it could also be a memory problem like I stated, but I have never said anything about a gamepad dude...
All I'm saying is that we should keep an open-mind about things without resorting to provokative posts so I apologize for me provokotive posting manner in this topic towards you.
However, I would like to indicate that I could be wrong, you could be wrong, the devs could be wrong, or we all can be wrong from a certain perspective, what makes you the "judge" of everything? Not trying to provoke, just asking.
Anyway, it could also be a memory problem like I stated, but I have never said anything about a gamepad dude...
All I'm saying is that we should keep an open-mind about things without resorting to provokative posts so I apologize for me provokotive posting manner in this topic towards you.
However, I would like to indicate that I could be wrong, you could be wrong, the devs could be wrong, or we all can be wrong from a certain perspective, what makes you the "judge" of everything? Not trying to provoke, just asking.
Last edited:
General Plot
Britchie Crazy
I know you didn't say anything about a game pad. I DID. Camera is controlled and manipulated by game pad manager, not graphics, how many times must I tell people this? The camera is separate from the graphics. What you are saying in essence would be the same as saying that if you move your character on screen and the game crashed, it is the controller that caused the crash, when in fact it was the graphics that caused the crash.
Edit: many emulators have to deal with similar type bugs. PCSX2 is quite the same. Many PS2 games use camera controls, but yet it's things like the IOP and VU (both graphics processors) being misinterpreted that cause all the crashes. I talk to the devs quite often, and they know where the bugs are (well most of them anyways) and they can fix one, but cause bugs in other places. Fix one thing, break ten things). I trust that the Chankast devs are aware of the "problem areas" but just haven't figured out how to fix it without breaking something else.
Edit: many emulators have to deal with similar type bugs. PCSX2 is quite the same. Many PS2 games use camera controls, but yet it's things like the IOP and VU (both graphics processors) being misinterpreted that cause all the crashes. I talk to the devs quite often, and they know where the bugs are (well most of them anyways
) and they can fix one, but cause bugs in other places. Fix one thing, break ten things). I trust that the Chankast devs are aware of the "problem areas" but just haven't figured out how to fix it without breaking something else.
Last edited:
The controller controls the graphics pitch, yes, but the graphics are still displayed VIA the camera, so the camera would have to be "in essence" related to the graphics in some way or form. You can't have the camera without the graphics, of course you could display a black background or something but you can't have it working without the graphics. Well you could, but it wouldn't be of much use. I never said it WAS the graphics, I said it was linked to the graphics aka "in essence" which I mean by "in part".
The controller moves the interface, which, is the camera, etc. It's a well in the real copy would be an external source that sends the information through the cord (unless it's wireless) which manipulates the inner code to tell it what to do. Sorry if this doesn't make sense, I got a little confused when I was imagining going inside a Dreamcast.
Anyway, all I'm saying is that it manipulates the graphics and in this "essence" case, it could be a piece of graphics that comes up that crashes it, maybe a certain pixel for all we know. We can't really tell what's actually up unless we were the devs and knew how they put it together. Need I say that all programs are programmed differently?
The controller moves the interface, which, is the camera, etc. It's a well in the real copy would be an external source that sends the information through the cord (unless it's wireless) which manipulates the inner code to tell it what to do. Sorry if this doesn't make sense, I got a little confused when I was imagining going inside a Dreamcast.
Anyway, all I'm saying is that it manipulates the graphics and in this "essence" case, it could be a piece of graphics that comes up that crashes it, maybe a certain pixel for all we know. We can't really tell what's actually up unless we were the devs and knew how they put it together. Need I say that all programs are programmed differently?
General Plot
Britchie Crazy
Need I say that the devs have already stated they know where the problem is, they just don't know how to fix it without breaking something else?
General Plot
Britchie Crazy
And regardless of whether the bug appears when a character is moved, or a camera is manipulated, it still comes down to a misinterpretation of the graphics. Solely graphics bugs. The idea that a camera control could fix/cause the problem is quite absurd really, and that was what I was trying to inform the original user who posted this thread. But after 4+ times of explaining the concept, it can be unnerving.
General Plot
Britchie Crazy
According to the authors, system memory is working as it should. The gfx memory is having some miswrites I believe it was. Don't quote me on that though, it's been a while since I checked the reports. This makes sense, since there is almost virtually no slowdown on most games, and yet graphics are missing and the likes. Just a note: I never said it wasn't a memory bug.
I'd also like to point out that I do what I can to help the community, and I encourage others to do so as well. I know the person that started this thread had good intentions, he just didn't understand what the problem was. Anyways, that aside, it seems like there are some rather nice improvements coming our way. Check the news thread for mor info.
I'd also like to point out that I do what I can to help the community, and I encourage others to do so as well. I know the person that started this thread had good intentions, he just didn't understand what the problem was. Anyways, that aside, it seems like there are some rather nice improvements coming our way. Check the news thread for mor info.
Last edited: