Welcome to Open Carnage

A resource for gamers and technology enthusiasts, with unique means of rewarding individual content creation and support. Have a wander to see why we're worth the time!

Sign in to follow this  
Followers 0
002

Proof of concept: Fixing the console fade time

In Halo, all of the console messages will fade after 150 frames. If the game is running at 30 frames per second, then it'll fade out after 5 seconds. If the game is running at 60 frames per second, then it's 2.5 seconds. If it's 120 frames per second, then it's 1.25 seconds. If the framerate is uncapped and it ends up running at 600 frames per second, then each message will go away after 0.25 seconds.

 

This plugin causes each message to fade out after 150 ticks, instead. Assuming the game is running at 30 ticks per second, each message will fade out after 5 seconds regardless of the framerate.

 

 

Currently I've only made a HaloMD version, because it especially affects HaloMD, as the framerate is set by default to Vsync.

 

As HAC2 already fixes it, I'm not sure about porting it to Halo PC/CE, as the default framerate is 30 FPS. Many people (possibly most people) are going to have the default frame rate, plus running the game faster than 30 FPS causes animation bugs which keeps a lot of people from running it any faster. That would mean this tool will not help these people in any way whatsoever, so it may just be a waste of time.

 

Any opinions?

Krazychic, Tucker933, NeX and 1 other like this

status.png?customhost=ProtonNebula.com:1

status.png?customhost=ProtonNebula.com:2

status.png?customhost=ProtonNebula.com:2

competent.png

Share this post


Link to post
Share on other sites

Dislike the ads? Log in or register to never see them again!

Not sure it's worth the time, to be honest. I can only imagine that the pool of players for MD is even smaller than that of PC/CE.

 

It's your time, if you think it's worth it, then have at. I'm just surprised anyone still messes with this stuff on a day-to-day basis :P

002 likes this

KsqHutE.png

Share this post


Link to post
Share on other sites

Not sure it's worth the time, to be honest. I can only imagine that the pool of players for MD is even smaller than that of PC/CE.

 

It's your time, if you think it's worth it, then have at. I'm just surprised anyone still messes with this stuff on a day-to-day basis :P

I kind of figured the same. However, HaloMD has been growing quite a bit over the past few years, and technically, anyone who has the frame rate set to anything higher than 30 FPS has this issue. Much more people on HaloMD would have a use for this than PC/CE users. I'd hate to make something Mac-exclusive, but I can really only conclude releasing this for PC/CE is nearly pointless.

 

I don't make this stuff daily or even monthly. I come up with a cool idea every few months or so, or I see a problem with Halo's engine and I want to fix it. As a result, I've made a bunch of cool things this way. Stuff like syncing biped locations (apparently this is good for AI), custom gravity (talking about bipeds, weapons, projectiles, equipment, etc.), syncing player velocity (you've seen it), and stuff like this are all very possible with a little bit of programming, but just aren't very useful. For instance, I know people have been wanting stuff like AI syncing since before Halo modding became a thing, but with how dead Halo PC/CE is, I guess it's simply not worth finishing.

WaeV likes this

status.png?customhost=ProtonNebula.com:1

status.png?customhost=ProtonNebula.com:2

status.png?customhost=ProtonNebula.com:2

competent.png

Share this post


Link to post
Share on other sites

I figured I should also add an additional feature that I felt was missing. Console text that has completely faded out reappears when you bring up the console again.

 

NeX, Tucker933 and WaeV like this

status.png?customhost=ProtonNebula.com:1

status.png?customhost=ProtonNebula.com:2

status.png?customhost=ProtonNebula.com:2

competent.png

Share this post


Link to post
Share on other sites

I'm almost torn now on how I want fading to work.

 

This is how it is right now:

 

Basically, it will unfade past console messages, and refade them when you close the console.

 

 

Then there is this:

 

Exiting the console will fade out all of the console messages, including new ones received when you were using the console. However, this will only affect you if you open and exit the console. If you receive a console message through something like a SAPP or Phasor script when you aren't using the console, this message will still begin to fade out after the usual time.

 

Most games won't have console messages lingering once you exit the console, which is why I'm considering this behavior. In my opinion, this is better.


status.png?customhost=ProtonNebula.com:1

status.png?customhost=ProtonNebula.com:2

status.png?customhost=ProtonNebula.com:2

competent.png

Share this post


Link to post
Share on other sites

Interesting stuff - never knew the console message fade was tied to framerate and that HAC2 fixed that. Since HSE® makes prolific use of console messaging on RW servers, this is good to know.

 

That console messaging is configurable - HSE® generates certain player-specific messages (ones that will never contain UTF-16 like player names), and there's a flag to switch those between chat and console.

 

It would be interesting to incorporate HaloMD's features in HAC2 or some other client-side mod. But my plate is full at the moment :)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0
  • Recently Browsing   0 members

    No registered users viewing this page.