http://www.moddb.com/games/doom/addons/brightmapspsx There will be all the information.
Only tested on Zandronum version, if you have something wrong in version Gzdoom talk me
Brightmaps for Psx Doom
Forum rules
The Projects forums are only for projects. If you are asking questions about a project, either find that project's thread, or start a thread in the General section instead.
Got a cool project idea but nothing else? Put it in the project ideas thread instead!
Projects for any Doom-based engine (especially 3DGE) are perfectly acceptable here too.
Please read the full rules for more details.
The Projects forums are only for projects. If you are asking questions about a project, either find that project's thread, or start a thread in the General section instead.
Got a cool project idea but nothing else? Put it in the project ideas thread instead!
Projects for any Doom-based engine (especially 3DGE) are perfectly acceptable here too.
Please read the full rules for more details.
Brightmaps for Psx Doom
DOWNLOAD HERE http://www.moddb.com/games/doom/addons/brightmapspsx
There will be all the information.
Only tested on Zandronum version, if you have something wrong in version Gzdoom talk me
http://www.moddb.com/games/doom/addons/brightmapspsx There will be all the information.
Only tested on Zandronum version, if you have something wrong in version Gzdoom talk me
Last edited by doomguy88 on Mon Apr 04, 2016 9:36 pm, edited 1 time in total.
-
wpninja
- Posts: 71
- Joined: Sat Oct 24, 2015 1:34 pm
- Location: On a far off planet by himself, killing demons.
Re: Brightmaps for Psx Doom
Oh Hell Yes!!! If there is one thing Doom mods and TC's need is more brightmaps, esp ones that focus on monsters eyes. I just hope that more brightmaps come along for mods such as project brutality and complex doom one day. Thanks alot man, very much appreciated. Can't wait to try them.
Re: Brightmaps for Psx Doom
This is great, but the sprite brightmaps are broken for version 2.135. Apparently the author modified all the sprites' sizes in the latest update. I hope this can be corrected on a version 3.0