Game Development Tools and Software
Home
Products
Torque 3D
Torque 2D
Store
Home
Genre Kits
Tools
Art Packs
Games
Community
What's New
Blogs
Resources
Forums
Dev Interviews
Made with Torque
Support
Documentation
Submit Bugs
Paid Support
Services
Education
Company
About GarageGames
Employment
Licensing
Licensing FAQ
RSS Feeds
Logo Guidelines
Contact Us
Register
Login
Cart
Game Development
Community
What's New
Blogs
Resources
Forums
SetColour() enhancement
by
bentgarney
·
in
Torque Game Builder
·
03/07/2005 (5:57 am)
·
1 replies
Torque Owner
bentgarney
Default Studio Name
About the author
Recent Threads
Minor bug involving setsize and mount with dummy sprites
Confirmed Mount bug leading to drastic slowdown
Torque and speedstep processors
What mac will T2D run on?
Why is directx rendering dx8 and not dx7
Next
Next Thread
Prev
Previous Thread
More from Torque Game Builder
Login to reply to this thread
Associate
Melv May
#1
03/07/2005 (5:57 am)
@Rob: This is from another thread. As I said in that thread, this function will be normalised in the future so you get a range of 0->1.
0 = Black / 255 = white, that's it. There's no "overbright". White is white, you can't make your monitor brighter or produce whiter.
Without graphics card support, you don't get higher dynamic ranges and even then, it doesn't work like this.
A glare on the screen isn't anything to do with this and hasn't really got anything to do with screen flashes or white outs.
I can divide the value you pass in by two and when you specify 512 it equals 255 which is full bright. It's all relative.
- Melv.
Login to reply to this thread
Post a blog
Add a resource
Start a Thread
All Products
3rd Party Addons
iTorque 2D
iTorque 3D
TGE
TGEA
Torque 2D
Torque 3D Pro
Torque X
Associate Melv May
0 = Black / 255 = white, that's it. There's no "overbright". White is white, you can't make your monitor brighter or produce whiter.
Without graphics card support, you don't get higher dynamic ranges and even then, it doesn't work like this.
A glare on the screen isn't anything to do with this and hasn't really got anything to do with screen flashes or white outs.
I can divide the value you pass in by two and when you specify 512 it equals 255 which is full bright. It's all relative.
- Melv.