Yes, there is VISR, and a few other things I believe. VISR, I know for sure because I've tried it.

Who gave you the installer?

Here's feedback:

OS messes up my FOV completely into almost making the game unplayable.
I also cannot access any of the F0-F12 keys which are supposed to bring up settings or something.
I have an azerty keyboard.

Sucks that you're using an unsupported version, guy!

I don't have any need for it, just giving feedback so you can make your software work.

If you were giving feedback on a recent build, maybe your posts would be helpful, but they're not. Which is why we didn't want pre-release builds floating around.

I apologise for trying to help you improve your software.

Though this makes sense, I would at least hear some of these bugs out before entirely discluding them; there could be issues that were undetected or uncorrected in recent builds.

Exactly, put aside your pride and take the feedback like a man.

We've already addressed said bug many, many revisions ago. Along with many other issues. Which is why we don't want pre-release builds just floating around out of control. People will encounter problems that will have already been fixed and post about it, only creating noise.

Working with a small group allows us to focus our testing efforts, and provide real-time help. We're not developing an entirely new game or some whatever CE map; we don't need mass play-testing.

Even if you're one of the most important guy of halo ce, kornmann...

...this is halomaps.

I'd like a stable version of OS soon tho, using fucntions that arent subject to change, but using leaks would be against my philosophy so I'll just sit there and wait.

There's no one important person in the community. Except Dennis. I hear his heart runs on Custom Edition v1.09. More people should update.

The installer that is floating around isn't a "leak" like most people are used to with maps (the source to the entire project is on code.google.com), it's just an unsupported build. It was made explicitly for our partnering with CMT and helping them make their mod of the campaign even better/complete. Even if the current code base runs in a stable manner, it doesn't mean the code is complete (FS hasn't finished working on his new shader code). Unfinished code means an unfinished product. An unfinished product means unfit for official release.

It's not like we have to rush to release OS to save CE or something. Releasing a month from now or a year wouldn't really make much a difference (not that we would wait another year, even if CMT had to for whatever reason). So we're taking the time to finish what we started. We're also waiting on a few external contributions that are being prototyped for consideration as additions into the official OpenSauce codebase.

Please take as long as you need to.

lol, don't expect anyone to help when you know its unsupported. You'll just have to figure it all out yourself.

If you type up os_ and then press tab you get an entire list of the available os commands in the console. (or maybe it was pp_ like waffles said above)
Pressing one of the f buttons will also bring up a list of video settings if it'll work on your pc I believe.

That's about all I know.
Edited by TM_updates on Nov 1, 2011 at 07:34 PM

^ idiot, if you know how to do something at least take the time to enlight everyone around you on how to do it instead of degrading them.

You have to use a new tag type in guerrilla and also import the VISR effect (I believe it is actually included by default though). I'm not exactly sure what to do with it from there, but I'm guessing a globals_yellow tag, in the biped, or scenario.

Those people don't really know anything, no offense to them. Those of us who have been working with it are the ones who are knowledgable about it, not people who have received an exe and then just tinkered with it.


Sorry butthurt buddy, but I'm not going to waste my time showing people how to use something that can be completely changing next week. CMT intends to share all our knowledge about OS and the things you can do with it, what we don't intend to do is give people information that is outdated and chainging, and in some cases incorrect based on what build you are running. Part of the whole idea of us using OS is so that we can support the community and help them with whatever questions they may have.

People should not be using old/WIP builds of OS for their content yet. For example with our maps, we had an issue where because of changes in OS, backward compatibility failed and it caused the game to exception on boot up. Everything was coded and implemented right, but things change and then they don't. Which is why if you want to use OS at this very instant, you will get no support until things are finally set in stone.
Edited by Masters1337 on Nov 1, 2011 at 09:12 PM
Edited by Masters1337 on Nov 1, 2011 at 09:23 PM

Is a martian stupid if he can't drive a motorcycle? No.

If you don't even have access to the support documents or developers, theres no way your going to have the same level of knowledge as someone who does. Give it time and you'll know everything we do, and don't start putting false words in my mouth. I'm going to be ended my involvement on this note, as I've said what I felt needed to be said.

But martians do drive motorcycles:

According to that martians are blue ? marks and motorcycles are invisible :p. Or it's the other way around.

You mad bro?

I'm pretty sure Kornman isn't going to go changing entire tag types when hes already taken his own and Firesycthes time already to do so and incorporate them.

Even if it were to change, you could have at least answered the man's question and expected him to be able to change along with the application and developers. Not helping people and telling them you do know how to do it is simply acting like an elitist, and quite frankly, a jerk.


Edited by Higuy on Nov 1, 2011 at 09:39 PM

I don't really want keep this "argument" alive, but I think some things need to be said, from our side of the fence at least.

We haven't finished adding all of the features CMT has requested support for. ChokingVictim is working on a few prototype ideas that will require the addition of new tag fields (thus changes to tag groups), or changes to existing ones, if they get approved for inclusion in the main codebase (chances are high that he will, he usually gets things done right before sending them my way). FS himself is working on finishing a new shader system which will use new tag groups. None of this new shader code or tags are even in the public codebase yet (in order to keep current things in working order, to name one reason). Most of my current and future changes are mostly based around some internal systems that only really affect other programmers, not users and designers.

Taking the time to explain things now isn't really worth our (at least mine and FS's) time as things will be changing. That time would be better spent building the wiki content to match the final release.

The build floating around is unsupported. No one should expect any short of help from CMT or us. However, that's not to say everyone deserves a nasty 'no soup for you!' reply. A few do, but not everyone.

Hopefully this can put the drama bombs to rest

Lol if you know how to help people NOW then just do so...

Lol, if you've done work on Lumoria's 2nd episode just release it now...

All right enough, back to work!
Mr. Aero doesn't want things to be delayed much longer because the involving parties felt they had to spent their precious project time on attempts to win meaningless internet arguments on the HaloMaps forum. :D

This is the final word on the subject so therefore the thread is closed. Next time everyone please check their egos and testosterone levels at the door before posting.