|
|
|
Tutorial for setting up Yelo15 Trainer for Halo 2 Screenshots!
|
|
Junior Member
|
6. October 2007 @ 06:44 |
Link to this message
|
|
awwwwwwww
what makes 1.6 so special?
so, it really doesn't matter if I have UX or EvoX, it's because of my kernel?
Like I've said before, SOME things work ... just with weird key combos. Possibly everything could work, with the right combination of buttons.
Is there any other devcam program for the xbox available?
|
|
Advertisement
|
|
|
|
Junior Member
|
6. October 2007 @ 07:03 |
Link to this message
|
how easy/hard is it to hack a 1.6 xbox? I may decide to get one, as my xbox is acting very strange. sometimes when I turn it on, it flashes the green light, etc...
http://forums.xbox-scene.com/index.php?showtopic=623785
What advantages (besides yelo) and disadvantages are there to having a 1.6 box?
|
Member
|
6. October 2007 @ 10:25 |
Link to this message
|
Ok, well apparently it's not the kernel of the xbox that matters. I just talked to a friend yesterday that claimed he had a V 1.0 xbox, and by simply changing the .ini file, he got it to work. But at the same time, his problem was just that it showed a black screen (aka, couldn't find the trainer).
So, I'm not so sure it's the kernel version of the Xbox that is doing it or not. Once again, if I had an Xbox that had a lower kernel, I would do some serious experimentations and find out.
To answer your question though, V 1.6 Xbox is just as easy to softmod as any other. The advantages to it, other than being able to use Yelo Trainer is that it is slightly faster, and doesn't freeze as often. Basically, it's just a little more stable.
I'm going to find out if my friend's console was actually a V 1.0 or not by getting him to check the kernel, as I think he may have been lying. Any more information I get on the subject will be posted immediately as it becomes available to me.
I'll keep you all updated, so don't worry.
|
Junior Member
|
6. October 2007 @ 18:09 |
Link to this message
|
|
thanks for the update, and thanks for your hard work!
I'm guessing you've moved, so ... how'd it go?
edit: I just checked out my xored.ini file, and I can't see anything that your friend would have changed, relating to any xbox version.
This message has been edited since posting. Last time this message was edited on 6. October 2007 @ 18:12
|
Member
|
6. October 2007 @ 19:42 |
Link to this message
|
|
Ah yes, the move went pretty good. We got everything there in one day, so it worked out as we'd expected.
I got the kernel number off of my friend's box, and I couldn't believe it. He actually does have a V 1.0-1.5 Xbox. So, I asked him for his Xored.ini file. I looked at it, and the only thing that had been changed in it was the game location. Not to mention, he's only ever had UnleashX dashboard installed.
With these results, I am baffled. It turns out that my very first conclusion, that it may be the dashboard, is false. It also turns out that my second conclusion that it was the kernel number, is also false.
With the new analysis, I am only led to believe that either some people are not following the tutorial properly, or, and this is just a far off guess, it has to do with the bios loader/patcher the user selected when softmodding their xbox.
So, my suggestions to those who are still having problems with Yelo Trainer, are these:
1. Re-download all files, and walk yourself through my tutorial again.
2. If the above doesn't work, you must Restore the C Drive (un-softmod your xbox). Then you need to completely re-softmod the xbox using the PBL-Metoo bios loader/patcher. This is, by far, taking a chance.
3. Set up a remote connection session with me so that I may take a look at all of your files, directories, and such, and make a special Xored.ini for you, and install Yelo myself.
I'm really uncertain at this point what would cause the Yelo Trainer to not work properly. I have now soft-modded over 5 different xbox systems, and installed Yelo Trainer on all of them without any problems.
Now, I just ask that if ANYBODY knows the real solution to this problem, please, let us know. Also, if anybody is willing to experiment with the above solutions, and gets any successful results, let us know.
Just a tidbit of another idea here. From what I've heard is happening (some functions working, while others are not, or the buttons are mixed up), may lead me to believe that it is possible that one of your controller ports are completely messed up.
|
Junior Member
|
6. October 2007 @ 20:18 |
Link to this message
|
|
"one of the controller ports messed up"
how about plugging the controller into port 2, or three, or four ... or 7? okay, maybe not that ...
yeah, you can look at/mess with my box - I think we're added to each other's y!IM, so I'll give you the info some time.
|
Member
|
7. October 2007 @ 17:14 |
Link to this message
|
Well, in real logic, your theory would work. However, in the way I am thinking that it may be broken is that it's sending a small signal to the xbox telling the xbox it's plugged in, but not working. Yelo reads the controller as being plugged in, or half-what, thus causing only some of the controls to work.
Once again, that theory is practically illogical, as the chances of a "shorted" wire are very small. This is really a problem I can't seem to figure out unless I can get my hands on a lower kernel xbox which has been shown to have not work with Yelo Trainer.
In the case that I can obtain one of the xbox consoles, I would definitely do some experimentation with it to see what is wrong. Again, the only thing that seems to be logical, is that the users having problems did not properly install the trainer.
EDIT: Another possibility has shown up in my research! The Yelo Trainer is intended for NTSC version Halo 2 disks. I ask that you check your Halo 2 disk, and see if it's NTSC or PAL. Maybe, just maybe, this could be the problem. Again, I'm not sure.
|
Member
|
7. October 2007 @ 20:07 |
Link to this message
|
UPDATE:
From what Ckasdf & I have found, the kernel of your xbox has NOTHING to do with getting Yelo 1.5 to work. Turns out he had a modified HDD in his xbox, and he had re-updated his Halo 2 after re-naming the $U folder (BIG mistake).
I can't stress it enough guys, MAKE SURE that the $U folder is renamed to ANYTHING else (unless you're using the multi-player map patch which requires it).
If you guys have any more problems, I'm still here. This just goes to show you that if I can get a remote session in, I can fix about anything (unless you unlocked your HDD, in which case, you're just screwed).
|
Junior Member
|
7. October 2007 @ 20:50 |
Link to this message
|
|
woooo, thanks for all the help man!
I shall rule the coolness factor!
or ... something. hah
but yes, remote sessions are AWESOME. :D
|
Member
|
7. October 2007 @ 20:58 |
Link to this message
|
|
Yeah, it probably could have been quicker if you had a faster internet connection ;-)
|
Junior Member
|
7. October 2007 @ 21:09 |
Link to this message
|
|
I'd be GLAD to upgrade my Internet connection ... if you'd be willing to finance it. ;)
|
Junior Member
|
7. October 2007 @ 22:39 |
Link to this message
|
|
/deleted/
SUMMARY: Devcam stopped working, I still have the new maps, I still have the "cheat" stuff - unlimited ammo/grenades, invincible, etc
EDIT: eh, forgive the stupidity - I forgot one of the biggest rules; only one controller while using dev mode
though to let you know ... the DVD receiver is not considered a controller, so it can stay in there.
This message has been edited since posting. Last time this message was edited on 7. October 2007 @ 22:51
|
Member
|
8. October 2007 @ 07:28 |
Link to this message
|
|
Well, I'm not so sure about that DVD Receiver thing. I think that if you have the DVD Receiver in the 4th controller slot, it won't matter; as for the others, I'm not sure. Either way, it doesn't really matter, if the devcam stops working, unplug controllers until it does start working. If it still doesn't work, unplug the DVD Receiver.
Maybe I should post a list of "Dumb mistakes you should never make that will help you keep your Yelo 1.5 Trainer working fine."
|
Junior Member
|
8. October 2007 @ 11:54 |
Link to this message
|
Hey ... I was doing more testing of all the different options for the devcam, and some things are weird, or don't seem to work.
*Vehicles; when developer's mode is turned on (in the settings @ start of yelo), driving vehicles becomes VERY weird due to the view.
Third person with shifted view helps some, but it's still kinda weird. First person shows through the vehicle, which is even weirder, and when in a bashee, has 0% visibility.
Any suggestions on how to drive a vehicle with the "proper" view (aka, the view given without the devcam)?
*camera depth & field of view
I've tried this while in a vehicle, it doesn't improve or even do anything. I've tried it on foot, no change. This seems to do nothing?
*Auto hires grabber
I know this is only in devcam view, but what does it do, exactly?
*Screenshot
Is this a continuous screenshot? What's the difference in this, and vidcap? I ask, because whenever I press screenshot, the hard drive continues to click, and the screen to lag for as long as the game is on. If I press the screenshot buttons again, it doesn't change; it still is seeming to take screenshots. How to turn it off, other than reset the box?
*ai toggle
What is this? I pressed it, nothing happened.
*Teleport
While this does work, it's quite slow...
*Secondary light vert/horiz in/decrease
What does this do?
*in/decrease secondary light brightness
This doesn't seem to have any effect
*Primary light vert/horiz in/decrease
again, what's it do?
*in/decrease primary light brightness
I got this to work a LITTLE bit during the gravemind cutscene, but no where else - and still, I couldn't see the environment the characters were in - just the characters, and the gravemind's tentacles
This message has been edited since posting. Last time this message was edited on 8. October 2007 @ 11:55
|
Junior Member
|
8. October 2007 @ 12:12 |
Link to this message
|
|
Is there any place I can read as to what exactly all the options in the yelo menu do? The skulls, ammo/grenade, etc are easy enough - but some of the options aren't self-explanatory
|
Member
|
8. October 2007 @ 17:01 |
Link to this message
|
A response to your questions has been posted below. If you have any more, feel free to ask. And yes, I should probably make a list with explanations.
Quote:
*Vehicles; when developer's mode is turned on (in the settings @ start of yelo), driving vehicles becomes VERY weird due to the view.
Third person with shifted view helps some, but it's still kinda weird. First person shows through the vehicle, which is even weirder, and when in a bashee, has 0% visibility.
Any suggestions on how to drive a vehicle with the "proper" view (aka, the view given without the devcam)?
Well, this is one of the many downsides of Yelo 1.5. I really wish they would release a Yelo 1.6, cause this annoys the hell outta me. It seems that, as long as you are even running the cam it does this. The only way to prevent it is to turn off the cam in the Trainer Options. I know, this disappoints me too :'-(
*camera depth & field of view
I've tried this while in a vehicle, it doesn't improve or even do anything. I've tried it on foot, no change. This seems to do nothing?
Try first freezing the game (aka, going into DevCam mode), and then see what this one does.
*Auto hires grabber
I know this is only in devcam view, but what does it do, exactly?
I'll re-word this one. "Auto high-resolution grabber". As far as I know, this will make every screen shot you take a high-res screen shot.
*Screenshot
Is this a continuous screenshot? What's the difference in this, and vidcap? I ask, because whenever I press screenshot, the hard drive continues to click, and the screen to lag for as long as the game is on. If I press the screenshot buttons again, it doesn't change; it still is seeming to take screenshots. How to turn it off, other than reset the box?
This shouldn't be happening. A screen shot is a screen shot, not a video. I would say, try unplugging that DVD Receiver for this one ;-)
*ai toggle
What is this? I pressed it, nothing happened.
This one will make you quite happy. AI = Artificial Intellegence. What this does, is if you are in campaign mode, and you toggle this, it will toggle the computer characters on and off to be dead and motionless, or to have a personality to want to destroy you. Also, this brings the other reason that Yelo 1.5 is notorious. You see, with this little tool, people can now make AI Characters onto multi-player maps, and actually have them work! There are a ton of these modded maps, you just have to look.
*Teleport
While this does work, it's quite slow...
Not slow the way I do it. First, enter DevCam (freeze everything), then move the camera to your location you want to go to, then press the magic buttons. Now return the cam to normal view, unfreeze the game, and if you didn't move, now walk forward and you should instantly be teleported. Again, I would try this with NO other controllers (including the DVD Receiver).
*Secondary light vert/horiz in/decrease
What does this do?
Enter DevCam mode (freeze the game), look at the master chief or whichever character you happen to be at the moment, and then try this. You will have the light of the holy god beating down on you.
*in/decrease secondary light brightness
This doesn't seem to have any effect
Same as above
*Primary light vert/horiz in/decrease
again, what's it do?
Same as above
*in/decrease primary light brightness
I got this to work a LITTLE bit during the gravemind cutscene, but no where else - and still, I couldn't see the environment the characters were in - just the characters, and the gravemind's tentacles
Same as above
|
|
VuLcMoDz
Suspended due to non-functional email address
|
2. November 2007 @ 20:38 |
Link to this message
|
|
i downloaded yelo trainer and it doesn't have mini folder
VulcanFury54311 Started modding on Halloween!
|
Junior Member
|
2. November 2007 @ 20:54 |
Link to this message
|
|
VuLcMoDz ... I'd suggest downloading it again. Because until you do, nothing's gonna happen with yelo. :P
|
|
V1474L17Y
Newbie
|
9. November 2007 @ 00:14 |
Link to this message
|
|
Hi, um i installed Yelo Trainer and got it to work fine, but I can do any of the pausing game, teleporting, taking pictures, fast game play, slow gameplay etc... and idk what im doing wrong, can any1 help me out? and also when i downloaded the Yelo i didnt have that mini folder, and idk if thats important or not, and also i dont have that $s folder either, so can any1 help me plz =]
|
Member
|
9. November 2007 @ 00:48 |
Link to this message
|
|
V1474L17Y - The "mini" folder is found with the Xored Trainer Launcher, not the trainer file itself. As far as it not working, you most certainly want to make sure you are using Xored Trainer Launcher and only have ONE controller plugged into the xbox at this time.
|
Junior Member
|
9. November 2007 @ 12:27 |
Link to this message
|
Originally posted by kslice917:
V1474L17Y - The "mini" folder is found with the Xored Trainer Launcher, not the trainer file itself. As far as it not working, you most certainly want to make sure you are using Xored Trainer Launcher and only have ONE controller plugged into the xbox at this time.
Why is ONLY one xbox controller required for this? Also, it seems that things act strange when the controller is not in port one (I found that out yesterday - due to the position of my xbox above the tv, it made better sense to plug the controller into port three, so the tv wasn't covered by the cable).
Plus, people keep talking about using some kind of built-in trainer in XBMC - but I don't know where it is or how to enable it, or whatever.
|
Member
|
9. November 2007 @ 15:14 |
Link to this message
|
|
I'm not sure why it only works with one controller, or the first control port for that matter. My guess is that each control port has a different coding to it and these signals will scramble if not read properly. The trainer is meant to only read the first one. Once again, that's just my guess, the source code for Yelo 1.5 hasn't been released :-/
As far as the built-in trainer launcher to XBMC, that applies to a certain version of XBMC. You have to remember, there are hundreds of different versions of XBMC made by other users. You just have to find that right one that has it built in.
|
Junior Member
|
9. November 2007 @ 16:50 |
Link to this message
|
|
If it only reads the first, why do crazy things happen when two are inserted then? :D
In addition, do you know which version of XBMC is with the trainer? I have the one from xbins, the one takled about in xboxscene.
|
Member
|
9. November 2007 @ 23:41 |
Link to this message
|
I do not know which version it came with, and I'm not sure why it does that when you plug in two controllers. As I said, I think it might have to do with the following:
Each control port is assigned a MAC Address, (just like your computer). When the trainer starts, it will read the MAC Address of the first control port, but will accept the data from the 2-4 control ports. However, it doesn't know how to decode this data, because it didn't read the MAC Address of these ports. If you have ever taken apart the xbox, you will find that each port is connected to a board. The 1-2 controllers are connected by 1 set of wires to a board, the 3-4 controllers are connected by 1 set of wires to the same board. The board is then connected to another board through a series of contacts.
It's all pretty complicated, and I'm not sure why it would be programmed this way. My guess is that it is because Yelo was originally programmed to aid in Video productions of Halo 2, and only 1-player video productions.
Again, I don't really have an answer for these questions, that is just my guess.
And again, I state, I have no idea which version, among the hundreds out there, of XBMC, have the built-in trainer.
|
|
Advertisement
|
|
|
Junior Member
|
10. November 2007 @ 18:45 |
Link to this message
|
|
just for technicallity, the controller ports don't have MAC addresses, though they do have some sort of address to distinguish them (they're really USB ports, just in a different shape).
In addition, while it looks like two ports have one set of wires, they really have two sets blended into one. They end in a plug that has two rows of wires - each row is for each controller. The yellow wire is special, but the other wires are standard USB.
That extra board that stands up, I think it's there for convenience.
|
|
