Jump to content
The Dark Mod Forums

Itches, Glitches & Anything Else...

greebo

By greebo
in DarkRadiant Feedback and Development

 Share

Recommended Posts

SneaksieDave

SneaksieDave

Posted
Posted

Great! Yep those are the two I found so far.

 

-About the clipping, oops :blush: yep I see it now.

-Version: I think the last I'd used before this was the 0.7 release; haven't been mapping much at all lately, though, so I'm rusty w/r/t DR and DoomEd both.

-fs_game: whether I click on startup or do so from preferences, the only option that shows up is Doom3 and I can only click it to accept. If nothing's changed, I'd assume it's not my path that's the problem (\doom3\darkradiant) because it seemed okay before.

 

I'm testing this under windows. Pressing 'N' only flashes the inspector briefly...you have to use the 'View' menu before it works.

Yep, I'm seeing that too.

  • Replies 1.9k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Tels
Tels

Since I've stumbled over the same issue (and even tracked a needless bugreport), I've just commited the following:   Index: def/tdm_mover_base.def ===================================================

rich_is_bored
rich_is_bored

That's a pretty ambitious project that will require almost every trick in the book. I can sort of envision how you might use fences, skyboxes, and archways to assist with compartmentalization but over

Sotha
Sotha

I'd say it is perfectly doable if you make it almost planar, or with only mild height differences. The images below show how I would do it:   See how the mountains and houses always block the view f

Posted Images

OrbWeaver

OrbWeaver

Posted
Posted
-fs_game: whether I click on startup or do so from preferences, the only option that shows up is Doom3 and I can only click it to accept. If nothing's changed, I'd assume it's not my path that's the problem (\doom3\darkradiant) because it seemed okay before.

 

You can only select Doom 3 from the global preferences, to get a mod you have to go File -> Project settings, select "Custom modification" and enter the "darkmod" name in the text box. This is perhaps a usability defect, as it seems to crop up quite often; feel free to raise it as such along with the other two bugs.

DarkRadiant homepage ⋄ DarkRadiant user guide ⋄ OrbWeaver's Dark Ambients ⋄ Blender export scripts

New Horizon

New Horizon

Posted
Posted

Found the problem. By default, DR came with both View Entity Info and ToggleEntityInspector bound to 'N'. Evidently, it didn't like this. One of those options needs to be removed, they both bring up the exact same window.

SneaksieDave

SneaksieDave

Posted
Posted
You can only select Doom 3 from the global preferences, to get a mod you have to go File -> Project settings, select "Custom modification" and enter the "darkmod" name in the text box. This is perhaps a usability defect, as it seems to crop up quite often; feel free to raise it as such along with the other two bugs.

Gotcha, that worked. Seems familiar too. Like I said, I'm rusty. ;)

 

Also, a clarification: on fresh startup (deleted the DR application data folder), I'm asked for the engine path - are they seeking the Doom3 path or the DR path? Because I browse to Doom3, and each time, it appends /darkradiant onto it. It's not clear which it wants.

greebo

greebo

Posted
  • Author
Posted
Found the problem. By default, DR came with both View Entity Info and ToggleEntityInspector bound to 'N'. Evidently, it didn't like this. One of those options needs to be removed, they both bring up the exact same window.

This is fixed on SVN.

 

Also, a clarification: on fresh startup (deleted the DR application data folder), I'm asked for the engine path - are they seeking the Doom3 path or the DR path? Because I browse to Doom3, and each time, it appends /darkradiant onto it. It's not clear which it wants.

The Doom 3 root path is required (i.e. C:\games\doom3). There have been cases where a subfolder is appended to the selected path (although it never happened to me). If this happens you can always edit the engine path via the Preferences to correct this.

greebo

greebo

Posted
  • Author
Posted
* Browsing some textures in the media browser and then closing DR causes an "Orphaned shader still referenced" assertion.

I'm currently refactoring the TexturesMap class (I'm roughly finished with textures.cpp, but not with the changes required to get the Overlay plugin running).

 

Should we try to fix this in the original texture browser or in the refactored version?

OrbWeaver

OrbWeaver

Posted
Posted
I'm currently refactoring the TexturesMap class (I'm roughly finished with textures.cpp, but not with the changes required to get the Overlay plugin running). Should we try to fix this in the original texture browser or in the refactored version?

 

I'm just going to remove that stupid assertion. Who cares if a texture is reference at shutdown? The memory will be reclaimed by the operating system anyway when the application is closed.

DarkRadiant homepage ⋄ DarkRadiant user guide ⋄ OrbWeaver's Dark Ambients ⋄ Blender export scripts

greebo

greebo

Posted
  • Author
Posted
* Activating mouselook with RMB, then switching between render modes, then right-clicking again gives an assertion failure ("free-move was already enabled"). This also messes up the mouse pointer -- I think there is a strong case for disabling the toggle mode and using a rightclick-drag mouselook that does not intercept mouse events.

This is also fixed on SVN now. :)

greebo

greebo

Posted
  • Author
Posted

I committed another feature to the overlay_plugin branch: the camera position and view angles are now saved to the worldspawn entity on map save. I tested it with maze1.map and it seems to work. :)

 

If the custom entity keys are not found, DarkRadiant falls back to the ordinary GtkRadiant behaviour (info_player_start is used as camera position).

greebo

greebo

Posted
  • Author
Posted

Orbweaver, can I already merge the changes from the overlay_plugin back into the trunk (now that 0.8.1 is released) or do you want me to wait with that?

greebo

greebo

Posted
  • Author
Posted

I merged your last commit into the branch, so it should be up to date. How do I merge the branch back into the trunk? Can this be done by choosing "Merge" from TortoiseSVN's menu or should I do this manually / in another way?

OrbWeaver

OrbWeaver

Posted
Posted

You should use the Merge command, yes. What you need to do is choose the URL of your branch in the URL box, and then select the range of revisions to merge -- which seems to be from 796 to HEAD. Note that when you select revision 796, the command generated wil actually start from 795 because you need then changes BETWEEN 795 and 796 to get the revision.

 

The equivalent SVN command is:

 

merge -r795:HEAD https://darkradiant.svn.sourceforge.net/svnroot/darkradiant/branches/overlay_plugin /path/to/local/darkradiant

 

What the command will do is calculate the diff between 795 and HEAD in that branch, and then merge that diff into your local working copy. Ideally there should be no conflicts when you do this, although I got one on user.xml (not entirely sure why) -- if you get loads of conflicts, you are probably not merging the correct changeset.

DarkRadiant homepage ⋄ DarkRadiant user guide ⋄ OrbWeaver's Dark Ambients ⋄ Blender export scripts

greebo

greebo

Posted
  • Author
Posted

Merged and committed as we speak. :)

 

The overlay module and the camera position restore is now in trunk. The camera restore could do with a bit of polishing (moving the player start entity key names into doom3.game and so on).

 

The current camera position is saved under editor_drLastCameraPos. Should I move this key name into doom3.game or leave it hardcoded as a constant (as it's not exactly game-specific)?

OrbWeaver

OrbWeaver

Posted
Posted
Merged and committed as we speak. :)

 

Excellent, I will check it out.

 

The current camera position is saved under editor_drLastCameraPos. Should I move this key name into doom3.game or leave it hardcoded as a constant (as it's not exactly game-specific)?

 

This should definitely go in the game file, since it could conceivably need to be changed for the game (if they key was used for other things, or something). Besides, hardcoding is evil and should be avoided wherever possible.

DarkRadiant homepage ⋄ DarkRadiant user guide ⋄ OrbWeaver's Dark Ambients ⋄ Blender export scripts

greebo

greebo

Posted
  • Author
Posted

Ok, the info_player_start eclass name is stored in doom3.game along with the two editor_drLastBleh keys.

 

I tweaked the handling of these editor-specific keys such that they are removed as soon as they have been parsed and therefore won't bother the user while editing the map.

greebo

greebo

Posted
  • Author
Posted

I'm currently changing the XMLRegistry to use two trees (it turns out to be quite straightforward, so I'll be finished soon).

 

Feel free to create a dialog, I've got some other tasks assigned in the bugtracker as well. :)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

  • Recent Status Updates

    • JackFarmer

      JackFarmer

      "The Year of the Rat." 
      😄

      Al Stewart must be proud of you!
      Happy testing!
      @MirceaKitsune
      · 3 replies
    • datiswous

      datiswous

      I posted about it before, but I think the default tdm logo video looks outdated. For a (i.m.o.) better looking version, you can download the pk4 attached to this post and plonk it in your tdm root folder. Every mission that starts with the tdm logo then starts with the better looking one. Try for example mission COS1 Pearls and Swine.
      tdm_logo_video.pk4
      · 2 replies
    • JackFarmer

      JackFarmer

      Kill the bots! (see the "Who is online" bar)
      · 3 replies
    • STiFU

      STiFU

      I finished DOOM - The Dark Ages the other day. It is a decent shooter, but not as great as its predecessors, especially because of the soundtrack.
      · 5 replies
    • JackFarmer

      JackFarmer

      What do you know about a 40 degree day?
      @demagogue
      · 4 replies
×
×
  • Create New...