eWallRim::Bound

Post by **Lucifer** » Sat Mar 11, 2006 2:07 am

Or he could just do the search in gCycle.cpp, that's where the headlight code is.

~|DS|~|Patch| · Post by **~|DS|~|Patch|** » Sat Mar 11, 2006 2:27 am

Where do you find the c++ files (and other ones of that nature)

Post by **Lucifer** » Sat Mar 11, 2006 2:34 am

Ahhh, you need to download a source tarball from the releases page. This is in 0.2.8, it's just disabled.

So, to build it, you need to go into gCycle.cpp near the top (it might be in gCycle.h), find the line that says "#define USEHEADLIGHT" and uncomment it, i.e. delete the "//" that's in front of it. Then compile the program and run it and you should have a new option in your HUD preferences to turn on the headlight.

This assumes you have a compiler all setup and ready to go with this. If you're in Linux, you're fine. If in Windows or Mac OS X, I don't know what you need to do, just that it's a bit trickier than in Linux.

Word · Post by **Word** » Mon Aug 24, 2009 5:10 pm

wow this is amazing

could you add this code to the next version and make it possible to turn off the headlights with a simple key (or console command?)

Jonathan · Post by **Jonathan** » Mon Aug 24, 2009 6:09 pm

Wow, somebody still wants this piece of novelty hack? Really, it's too hacky to make it into a release without being reworked. It can do anything from just looking wrong to … anything? (like crash if you're unlucky)

Word · Post by **Word** » Mon Aug 24, 2009 6:28 pm

ok that's sad

compguygene · Post by **compguygene** » Mon Aug 24, 2009 6:53 pm

@Word, since I don't think that you have ever written any code, let me explain. In general there are to ways to add a function to an application.

Way#1 make a quick hack that could cause the entire code to crash, or other weird effect.

Way#2 Spend a lot of time writing code that can safely be added to the code for future releases.

Jip · Post by **Jip** » Thu Jan 17, 2013 9:12 am

Sorry to bump this old thread.
I saw that the code is still is in the source and I tried to activate it. I uncommented #define USE_HEADLIGHT in gCycle.h and I got the option to activate/deactivate headlights. But it changes nothing.
Is there more code I need to add or activate?

delinquent · Post by **delinquent** » Thu Jan 17, 2013 2:35 pm

Trying it it code:blocks

Where you see #ifdef USE_HEADLIGHT, below that block there is another function "#endif // USE_HEADLIGHT". Currently, I'm going to try unquoting that, since use_headlight is already unquoted? You may have more success than me.

Edit: There appears to be no "#define USE_HEADLIGHT", but "#ifdef USE_HEADLIGHT" is credited to Jonathan.

Jip · Post by **Jip** » Thu Jan 17, 2013 7:08 pm

delinquent wrote:[...] there is another function "#endif // USE_HEADLIGHT".

It's not a function, it closes the #ifdef USE_HEADLIGHT statement.

Jonathan · Post by **Jonathan** » Thu Jan 17, 2013 9:28 pm

I suspect the problem is that it resets the modelview matrix. Until recently that only undid the slightly unpredictable cycle transform, but now it undoes the camera as well, causing it to be misplaced. If you are using a recent version, try downgrading because I'm not fixing this thing.

delinquent · Post by **delinquent** » Thu Jan 17, 2013 10:26 pm

Jip wrote:
delinquent wrote:[...] there is another function "#endif // USE_HEADLIGHT".
It's not a function, it closes the #ifdef USE_HEADLIGHT statement.

Pff, I'm nab at this stuff. I thought that might be the case, but then why is there a block of code seemingly related to the headlights underneath the closing parameter?

Jonathan · Post by **Jonathan** » Thu Jan 17, 2013 11:07 pm

Underneath the #endif there is no headlight code. There's the name tag, the cycle's shadow, and the lag-o-meter.

Armagetron Forums

eWallRim::Bound

Re: eWallRim::Bound

Re: eWallRim::Bound

Re: eWallRim::Bound

Re: eWallRim::Bound

Re: eWallRim::Bound

Re: eWallRim::Bound

Re: eWallRim::Bound

Re: eWallRim::Bound

Re: eWallRim::Bound

Re: eWallRim::Bound