Jump to content
The Dark Mod Forums

shadow_ibix

Member
  • Posts

    24
  • Joined

  • Last visited

Everything posted by shadow_ibix

  1. Nice to play. Still missing some easter eggs, so I should hunt around.
  2. Nice mission. TDM can do huge forests! With buildings! And large castle! And you can save a magical fantasy kingdom
  3. The komag mirror seems to have a partial file: Picking mirror KeepOfMetalAndGold Downloading to temporary file D:/Games/Doom 3/darkmod/__tdm_update_1.02_to_1.03.zip Initiating Download from http://www.keepofmetalandgold.com/files/tdm/tdm_update_1.02_to_1.03.zip Download failed: Transferred a partial file Connection Error. Removed file D:\Games\Doom 3\darkmod\__tdm_update_1.02_to_1.03.zip It was quite far along its 214.7 Mb download, but then failed and now uses another mirror.
  4. It means the word is wrong, but you put it there intentionally. Sorry for the offtopic to spelling The illusionists tower is very nice. I was not able to sneak attack a spider with the sword, but had to use the bow.
  5. Works, quicksave and load fine, rope arrows fine. TDM 1.02. Berny, more direct
  6. It was my experience some time ago with particles, especially if large (10% of screen) and a lot (hundreds). It depended on the hardware - with newer but also different manufacturers working better. Basically it needs more 'pixel math', and thus has a bigger influence on the FPS. So go ahead and use it, because it is what you want, but I wanted to caution against too-much, too-large. Also, I think with AlphaTest 0.4 or 0.8 or so, you can change an alpha-ed texture from blurry edges to one with sharply defined edges, like for a fence, when you look up close. Yes, but the doubling causes colour-changes. Its not HDR
  7. Nice link to other thread, from the screenshot of the particle editor, I would suggest: Distribution set to whatever (pretty close together, like in the output tube of the faucet). Direction/Orientation: set to cone, use the angle with a reasonably small value for a 'tighter' fountain, in direction Y (upwards, like a fountain). Check the World Gravity button to enabled, with -10 could be good. Set the speed relatively high, 20 or so (no randomness needed, your cone provides the fountain shape), and 0 rotation, 1 aspect, and some fixed size other than 0. Thus particles start in the small faucet area, with an initial direction to move in a cone upwards and in a circle outwards, then go down with gravity. Well that is the idea, not sure if that works .
  8. With blend modulate, the colour bright white on your texture turns see-through. Black is shadow. It is good at creating shadows. With blend add, the colour black on your texture turns see-through and everything is glow-in-the-dark. It is good at magical effects. But I think what you want is blend blend It causes your texture to be copied to the screen, and the alpha channel of your texture is used normally to fade into the existing background. This is more expensive, so do not make hundreds of very large particles as this may cause slowdown (on lower spec machines). Since I am going over the options, the setting blend gl_dst_color, gl_src_color is also useful, like modulate but you can also create areas where 'there is more light', with a texture where white adds light, black adds shadow and gray is transparent. This sort of setting, or blend modulate (which is the same as blend filter) is good with a 'baked' lightmap that was output from a 3d editor program (where the 3d editor creates a black and white texture with the shadows on it for the object you made, since the 3d editor program can sometimes output much nicer shadows than doom3 would be able to render realtime). Of course, you want to create a droplet of wine, not light or darkness, and thus the blend blend mode which copies your texture represents what happens; you see the droplet you draw on the texture.
  9. Very nice, also, one of the plants in the early gardens has its polygons facing inwards, black on the outside and lighted on the inside. Mission is excellent in the dark mod, since
  10. That was a lot of fun for a test of the editor
  11. Gorgeous missions, large sprawling areas. I mean, large areas, not tiny cramped and full of loading zones. One of the zombies from the pit managed to 'walk' up into the little room on the far right, when they were alerted and I had just jumped into that room. Waited a little bit, and it fell back down again... Zombies are scary, so this was fine mood enhancing. But perhaps not intentional? I noticed that blackjacking seems to get harder if the CPU is busier. Or framerate is low. Anyway that was about 1.01. This campaign has beautiful environments, each nicely done.
  12. A cheap trick, depending on how the human eye (and its mental processing) really works, could be to simply take an edge-detect (like the gimp-plugin), and use that to provide details. The direction of the change is wrong half the time, but just like all those GUI controls with fake-3d outlines where inset or outset does not really matter, it may look nice to people. More realistically, having written software 3d-renderer bumpmapping, I would look for circular spots on the image (scan through), where you can detect a 'highlight' effect. Highlights come in two flavors: metallic and non-metallic, and you can see based on the colour of the light and colour of the highlight (ignoring iridescence). based on a 5x5 region around a pixel, say, you then calculate the angle of the highlight based on the position of the white 'spot' or 'stripe', I would do this by making a weighted average of the angular vector based on every 'highlight' pixel's intensity, position relative to the center pixel. Similar but inverse for 'shadows' (black). You end up with angular vectors for every pixel, which are smoothed because of the 5x5. Perhaps 5x5 is small and produces not much variation in bump vectors. If you want to get fancy, you would want to integrate with edge detection, detect surfaces or regions in the image with a similar texture, i.e. similar highlight and shadows, and use that information as well, and so on. Sorry if this is rambling off on an idea
  13. Very nice, long, mansion mission. Good, moody, backgrounds. And intricate storyline.
  14. In another (opensource) 3d engine alpha-stuff was solved by having different draw phases. One phase draws all solid materials to set up the Zbuffer, and the next phase draws all alphatest (and alpha without testing as well) in back-to-front (in reference to the screenspace) order. This draws the transparent objects fine (with some exceptions that do not happen a lot unless you make everything transparent; to make even better you'd want the 'stencil type' alpha to fill Zbuffer (a railing) and for 'blend style' alpha to not fill Zbuffer (for glass or fog, its fine to underlap; perhaps with pixel shaders you can make it test and if alpha=99% solid for a pixel then fill Zbuffer)). If the engine uses blend_add and blend_mult apart from simple 'png-style' alpha you can make passes for that as well, so that add and mult and alphablend give the desired color formula; like: alphablend(railings, windows), mult(shadows) then add(fireworks). Anyway, all this complication is not really needed, for an editor, sort back-to-front with the octree and render another pass for the alphastuff with ztest. Sorry if this is too much detail on it
  15. Hi Xonze, Oh gosh, Thanks finished missing 60 loot I think this is a really nice 'mansion-style' mission, and it is very impressive that you did this in two weeks.
  16. Very nice mission - nice look, interesting guard placement. Playing on difficult. Cant find the right bedroom key, where can you get it? Searching did reveal:
  17. Recompiled, and the previous warnings are fixed I had to re-run autogen.sh to recreate radiant/Makefile.in otherwise you get missing symbol errors in linking, you patched the Makefile.am but autogen.sh needs to run after that. Hm I'm not allowed to attach .patch.gz files. http://rapidshare.com/files/295706778/trunk_oct20_autogen.patch.gz.html Well, I have compiled again and included all the warnings I left out previously. Signed/unsigned trouble, and lots and lots of strict-aliasing errors. The most important are a couple unsolved 'result unused' warnings, like that *bp++ we discussed above. http://pastebin.com/m58de8cf
  18. No the warning is one line lower. On the *bp++; This is incrementing the handle (the function argument) which gets discarded at function exit. The * in there serves no purpose, hence the warning. The result of the increase is also never used ... Now if it was (*bp)++; then the pass-by-reference pointer gets incremented. I do not understand your code well enough to know if this routine gets passed an array of pointers and it cycles to the next pointer in the array, if the (**bp)++ data value needs changing, or if (*bp)++ the pass-by-ref-ptr needs moving, or the statement simply needs to be discarded. If this one was off one line, you might check at other 'nonsense'warnings if the next line has it. I'll see about recompiling.
  19. Had the same, with an ATI card, and turning off bloom fixed that, but turning off ATI Catalyst A.I. fixed it even better - the skyportal worked as well and I could turn on bloom again
  20. Nice map, fun to play. Apart from the rafters, I searched the coal for diamonds with the lantern for a while . Tried to snip off some banners as well, but that does not work. I'm happy to leave the banners, they make the place look pretty.
  21. The compiler here generates some warnings that your compiler may not. I have collected the ones that I think may be bugs/oversights/possible signs of problems: http://pastebin.com/m2c3e7066 I left out signedness warnings, pointer-conversion warnings and breaking strict-aliasing rules (type punned pointers). Well, except for that float pointer to double pointer warning, which looks like it is a real bug. Yay for gcc 4.4 .
  22. Yeah that would be neat, here is a patch with $(BOOST_SYSTEM_LIBS). It works for me. You have to run autogen.sh again to rebuild configure after this patch. Thanks for quickly replying to the other patch Index: configure.ac ======================================== =========================== --- configure.ac (revision 4850) +++ configure.ac (working copy) @@ -101,6 +101,12 @@ [AC_MSG_ERROR([boost.Filesystem not found])]) AC_SUBST([bOOST_FILESYSTEM_LIBS]) +# Boost.System +AC_CHECK_LIB([boost_system], [main], + [bOOST_SYSTEM_LIBS='-lboost_system'], + [AC_MSG_ERROR([boost.System not found])]) +AC_SUBST([bOOST_SYSTEM_LIBS]) + # Boost.Python if required if test "$python_scripting" = 'yes' then Index: plugins/script/Makefile.am ======================================== =========================== --- plugins/script/Makefile.am (revision 4850) +++ plugins/script/Makefile.am (working copy) @@ -6,6 +6,7 @@ modules_LTLIBRARIES = script.la script_la_LDFLAGS = -module -avoid-version \ + $(BOOST_SYSTEM_LIBS) \ $(BOOST_FILESYSTEM_LIBS) \ $(BOOST_PYTHON_LIBS) \ $(PYTHON_LIBS) \ Index: plugins/vfspk3/Makefile.am ======================================== =========================== --- plugins/vfspk3/Makefile.am (revision 4850) +++ plugins/vfspk3/Makefile.am (working copy) @@ -5,6 +5,6 @@ modules_LTLIBRARIES = vfspk3.la vfspk3_la_LDFLAGS = -module -avoid-version \ - $(GLIB_LIBS) $(XML_LIBS) $(BOOST_FILESYSTEM_LIBS) + $(GLIB_LIBS) $(XML_LIBS) $(BOOST_SYSTEM_LIBS) $(BOOST_FILESYSTEM_LIBS) vfspk3_la_SOURCES = vfspk3.cpp Doom3FileSystem.cpp DirectoryArchive.cpp
  23. On Fedora, compiled darkradiant-trunk (from today). I had to fix some things to compile, see the codebox below. fixes to fix 'EOF not defined', and two to link with libboost_system. After you apply these, run ./autogen.sh to have ui/einspector/PropertyEditor.cpp included in the makefile and also to propagate the fixes to the Makefile.in files. Then configure again to propagate them to the Makefiles and then make to use them. With these adjustments, it compiles for me (32 bit). ======================================== =========================== --- radiant/log/LogStreamBuf.cpp (revision 4849) +++ radiant/log/LogStreamBuf.cpp (working copy) @@ -1,5 +1,6 @@ #include "LogStreamBuf.h" +#include <stdio.h> #include <stdexcept> #include "LogWriter.h" Index: include/itextstream.h ======================================== =========================== --- include/itextstream.h (revision 4849) +++ include/itextstream.h (working copy) @@ -27,6 +27,7 @@ #include <cstddef> #include <string> +#include <stdio.h> #include <streambuf> #include <istream> #include <cassert> Index: plugins/vfspk3/Makefile.am ======================================== =========================== --- plugins/vfspk3/Makefile.am (revision 4849) +++ plugins/vfspk3/Makefile.am (working copy) @@ -5,6 +5,6 @@ modules_LTLIBRARIES = vfspk3.la vfspk3_la_LDFLAGS = -module -avoid-version \ - $(GLIB_LIBS) $(XML_LIBS) $(BOOST_FILESYSTEM_LIBS) + $(GLIB_LIBS) $(XML_LIBS) -lboost_system $(BOOST_FILESYSTEM_LIBS) vfspk3_la_SOURCES = vfspk3.cpp Doom3FileSystem.cpp DirectoryArchive.cpp Index: plugins/script/Makefile.am ======================================== =========================== --- plugins/script/Makefile.am (revision 4849) +++ plugins/script/Makefile.am (working copy) @@ -6,7 +6,7 @@ modules_LTLIBRARIES = script.la script_la_LDFLAGS = -module -avoid-version \ - $(BOOST_FILESYSTEM_LIBS) \ + -lboost_system $(BOOST_FILESYSTEM_LIBS) \ $(BOOST_PYTHON_LIBS) \ $(PYTHON_LIBS) \ $(GTK_LIBS)
×
×
  • Create New...