I know Kornman and TheGhost have their hands full right now, but i thought we should make a list of everything we want that would improve h2vista further. To start it off i think there should be a custom sound compiler.
Printable View
I know Kornman and TheGhost have their hands full right now, but i thought we should make a list of everything we want that would improve h2vista further. To start it off i think there should be a custom sound compiler.
Uhh, what do you mean by maker. If you mean actually creating sounds they probly won't make that. Compiling sounds into halo 2's format is probly available with an unlocked tool mb. TBH, there aren't THAT many programs to be made, they already exist(ex: 3d modeling tools, sound creation, etc..). Any that need to be made that actually deals with halo2 and improving it, they will think of or already are in progress.
First of all, I think most of the community realizes that Korn and Ghost aren't their employees. They're not going to help you whip up a list of 'things to do.'
Second of all, if we did, do you honestly think they would take it seriously? I mean, c'mon man - they don't have to take orders from anyone, they're doing this out of their own free will.
i didnt mean ity that way... i guess i shouldve called it: Tasks That It Would Be Appreciated To Be Accomplished By The More Talented Of The Halo Programming Community
It's rude of you to ask something like this of them. I don't think you quite understand the amount effort it takes, especially since you want to create a thread full of things that people want. The programmers are giving up their time to help us as it is, so don't push it. I really appreciate what the skilled programmers around here do. There aren't a lot of them, but they make a huge difference. Be patient, they are only going to work on what's most important.
ok...ok... i guess when i heard about what they were doing i did get a bit excited and greedy...
The truth of the matter is, and I'm not saying this to sound mean or anything, but we generally just work on what interests ourselves, what we have experience with, and that dictates what we spend our time on. Korn's expertise is with reverse engineering and the like, while I mostly work with 3ds max scripts. Sometimes -- many times -- our interests will collide and that really helps with progress. Korn may ask me to do something or I might ask him, but that stems from mutual respect and a sense of helping each other out. A laundry list, a wishlist, of to-do programs really doesn't help much at all. My best advice to anyone wanting something is to give it a shot yourself. And that's for a number of reasons that should be pretty obvious upon reflection.
ya, srry, no offence taken
EDIT: just out of curiosity, do you have a job that relates to this or do you do and did you learn this for fun
Collision model hce to h2v upgrader. I'm thinking of bundling it with the final release of my model upgrader, but I don't know if anyone else has started work on one. I found out the collision models are more identical in hce to h2v than the render models are so upgrading won't be as hard or buggy.
Memory hacks are all on hold until we can find out how to get the base address of a program. All the addresses are halo2.exe+offset. We know the offsets, but halo2.exe always changes.
Bitterbanana can code it if we gave him the address, but I bothered him too much about it :V.
Its a balanced trade off as widening your FOV decreases the size of objects displayed making distances things harder to see. Increasing your graphics quality, and screen resolution pose more of an advantage than just FOV adjustment. A no, a FOV hack, or any hack is not illegal by any means.
I just wish I could find someone I could trust to help me remake Engine Room. Everyone so far has just said "ok i will do itz ^_^!!111" then gone off to do some other shit. Maybe then I would listen to what they have to say as far as utilities go.
o.o He was answering a question...
FOV hacks are generally unfair because its an unintended advantage. I don't care how small things look -- it'll be larger than a pixel so you'll be able to see it when you shouldn't.
I didn't really see anything rude about asking for features. Everyone knows no-one would care, however there's no harm in asking; its obvious he wasn't just being a demanding n00b.
you guys whatever they come out with will be fine and asking more from them is not appropriate. The only thing I have to say is a help file would be nice:):).
A tutorial even better. (thats a long shot):lol:
How about an FOV hack with fixed limits? That way, people couldn't increase/decrease it as they please - they would just have two options: 'on' or 'off.' I mean, at least 90 degrees would be pretty nice. What's H2V's FOV?
The max is 110 degrees I believe, but then you start to see the entire model of the arms and just looks ugly. It is orginially at 70 degrees.
what's the FOV settings that look like the FOV for Halo 3?