Jump to content

Search the Community

Showing results for tags 'mapping'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Discussion
    • News & Announcements
    • The Dark Mod
    • Fan Missions
    • Off-Topic
  • Feedback and Support
    • TDM Tech Support
    • DarkRadiant Feedback and Development
    • I want to Help
  • Editing and Design
    • TDM Editors Guild
    • Art Assets
    • Music & SFX

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 6 results

  1. Hey! I hope this is the right section for this. I'm currently working on my first mission, entitled The Joyau Rouge. I haven't really got anywhere with it yet apart from the planning, because of what's either a bug or me being stupid. I'm running Siduction (a Linux distribution based on Debian unstable) and I don't seem to be able to free-look using the camera in DarkRadiant. I've attached a video of it—the context menu and dialog box are invisible in the recording, but at the start I'm adding a prefab. I hope someone can help me get around this issue. Thanks! —Xaeman 2020-11-26 21-46-44.mkv
  2. In the vein of a few other threads, I've decided to start a thread that will cover the current progress of my FM mapping and serves for troubleshooting the issues I run into. While the newbie questions thread is a good place to seek advice, I often get the impression that it's not adequate to solve the perennial mistakes I seem to run into while trying to learn certain aspects of mapping. I'll gladly welcome any advice in this thread. Screenshots of what I'm currently working on coming soon.
  3. Hi guys. This is my first post. I'm using DarkRadiant 2.0.2. I've run into a problem with Visportals or I'm doing something wrong. DarkRadiant seems to delete the brush I've made for Visportals after clicking on Make Visportal. Applying the Visportal texture also seems to delete the brush. I'm going to try the DarkRadiant 2.0.3 pre-build.
  4. Not sure where else to write since TheDarkMod forums is the only remaining outpost for Doom 3 modding. I need to make a mover to move along a spline, when triggered. How do I set it up? Can a mover tilt, following spline's curvature ? Is there a way to attach player to that mover and drop player if he presses a key ? Thanks!
  5. So, as everybody seems to have his own mapping thread, I thought about starting my own. I'm currently working on my map for the "unusual gameplay contest" and just set up a nice working elevator. I took a look one the multi-level elevator tutorial on the wiki and I think that my approach is much more easy to implement, so I thought I could describe it here. The elevator consists out of three parts: - a func_mover entity that will be our elevator-platform - the buttons that will control the elevator - a couple of waypoints, one for each floor what else do we need: a really short script, I'll go to explain further down The first step is to create an elevator-platform. This is your part . If your done with it change its classname to func mover (under entities/func/movers). Rename it to platform. (The names are for referance. Of course you can choose them as you like). The next step is to create some path_corner entities and place them, where you want your platform to stop. Be aware that the origin of the platform entity will move to the center of the bottom face of the pink block representing the path_corner. Let the platform target the path_corners. Make sure you start with "target0", then "target1" and so one. Start with the lowest path_corner and move upwards level by level. Create buttons for every floor on one of the levels. For the other you can just copy them around when we've set them up. On the buttons, you have to set three spawnargs. - target: let the buttons target the platform (so you have to insert its name here) - state_change_callback: set this to "movePlat". This is the name of the function we'll use to move the elevator - moveDir: set this to "0" for the lowest button, "1" for the next one and so one. This spawnarg controls which path_corner the platform should move to When you're done, copy the buttons to where else you'll need them. Ok, that's the setup in Dark Radiant. Now everything that's is needed is a script. And here it is. void movePlat(entity button,boolean bOpen,boolean bLocked,boolean bInterrupted) { entity mover = button.getEntityKey("target"); entity target = mover.getEntityKey("target"+button.getKey("moveDir")); mover.moveTo(target); } The "state_change_callback" is called everytime when the state of the specific object was changed, for example if a button is pressed. The function receives four arguments, of which we will only need the first one. The entity that we get here is the one who has called the script. In this case, the button we have pressed. Now what does the code do. The first line brings us the entity targeted by the button. This is our platform. We need to know this as we want to make it move The second line gives us the path_corner the platform should move to. Here you can see why you should start targeting them from 0 upwards and what the "moveDir" spawnarg is used for. An example: If you push a button whichs "moveDir" spawnarg is "1", than the platform targeted by the button will move to the path_corner targeted by the platform via the spawnarg "target1". The last line is quite self-explaining. It tells the platform to move to the designated path_corner. That's it. Pro's: - short code that is used for every elevator in the map (in fact you can use it for everything that translates) - fast setup Con's: - As I didn't tested it very much I don't know any if you find some please report here What is missing: - there are no sounds set up yet (will add them as soos as possible) - AI's should not yet be able to use the elevator (dido)
  6. I was looking at some images we have posted after taking some time away from computers entirely for quite an extended period of time and there's one thing I noticed. When we have specific brick or cobblestone textures they look fairly flat and bland. Maybe we should revisit the idea of parallax mapping, it would really improve these textures and actually increase performance because mappers wont need to use polygons to make convincingly 3d cobblestone and brickwork. We don't need parallax for all textures, this is one of the things TDS did right. Some textures had parallax some didn't, why don't we do the same, is this a good or bad idea?
×
×
  • Create New...