I want to darken the whole map in global shading mode / lightmode x, but it doesn't work. I want to darken the whole map before I insert lights, so I press CAPS LOCK, but nothing happens :( It won't get darker than this: http://i225.photobucket.com/albums/dd202/highwingx3/notdarkenough.png
I must use the other lightmode (the one without realistic shadows). I'm tired of lines like these: http://i225.photobucket.com/albums/dd202/highwingx3/ASDFFDA.png There must be an easy way to completely darken the map in lightmode x..
:'(
Awesoken at
Re: VOXED: Why can't I "Darken all intensities on map by 25%" in lightmode x?
Flashing in shading mode 0 has shadows, while shading mode 2 does not. Those lines are artifacts of my shadowing algorithm. The ambient lighting level in shading mode 2 is hard-coded. Search for the constant 47.5 in VOXLAP5.C - this is your culprit. Note that shading mode 0 supports a 2nd, older, "flash" function: Alt+F, which may have fewer artifacts.
ConsistentCallsign at
ALT-F in shading mode 0 has indeed fewer artifacts, but it makes VOXED crash :( I got the following error:
initdirectdraw failed: 0x88760245
ALT-F gives a much better result: http://i225.photobucket.com/albums/dd202/highwingx3/ASFGSDAFFF.png But too often it crashes voxed! :'( It's impossible to use the alternative flash in the bathroom, for example..
I have an Athlon CPU by the way.
Edited by ConsistentCallsign at
Awesoken at
That error message makes no sense, since Voxed only calls initdirectdraw at the beginning. Something must be horribly corrupt.
ConsistentCallsign at
Is it easy to make a program that scans .vxl files and repairs/replaces corrupted/damaged voxels? ???
Using alt-f in the default Voxlap map that Tom Dobrowolski made (the one with the worm and the walking woman) does NOT make voxed crash, it only crashes on other maps like the voxelstein castle tech-demo map..
Using F in lightmode 0: http://i225.photobucket.com/albums/dd202/highwingx3/lightmode0f.png
Using Alt-F in lightmode 0: http://i225.photobucket.com/albums/dd202/highwingx3/lightmode0alt-fb.png http://i225.photobucket.com/albums/dd202/highwingx3/lightmode0alt-f.png
The alternative flash produces sharper image quality, clearer depth/perspective and less lines/artifacts that are annoying.
What if there is something wrong with the alt-f algorithm that make voxed crash when weird/complex voxel surfaces are present?
Edited by ConsistentCallsign at
ConsistentCallsign at
If I remove all the voxels in my map that is "corrupted/weird", I can use alt-f again without crashing voxed.
ConsistentCallsign at
Is the alt-f problem easy to fix? Will hansk be able to help me?
Jack Bauer said
It is imperative that the maps in the next release are lighted with alt-f instead of f!
:D
Dany at
I know that this is a very old topic but it'd help if you'll just make gamma 25% smaller:) P.S.: I know that it's possible with one function of DirectDraw but I'm scared, because it's first time that I can't find a DirectDraw function!!!