Jump to content
The Dark Mod Forums

hypov8

Member
  • Content Count

    29
  • Joined

  • Last visited

Community Reputation

1 Neutral

About hypov8

  • Rank
    Member
  1. i was looking for surface inspector shortcut to H/V shit size, but found some isues MoveSelectionUP is crashing DR when nothing is selected. on a fresh load bound key to "PLUS" is not working. need to be rebound to "=" Maybe a regon issue? im using US for keyboard in old radaint there is an option to match surface inspector H/V shift value to match grid size could this be implimented. instead of manualy typing values thanks david
  2. thanks for implimenting the mouse pan in 3d there is an issue on my setup tho, moving up/down is reversed maybe some conflicting option i have?
  3. this is the laggy brushes i was referring to. not sure if others are haing the same issue? comparing pre10 to an older build https://youtu.be/UznQ8mXr8qM i do have another suggestion with the 3d view port. when you are in free look mode and hold ctrl, the view pans. would it be possible when not in free look mode, hold ctrl, then use right mouse. it should enter pan mode but not free look. so once you let go of mouse 2 it return the cursor. this might cause an issue if ctrl is let go first.
  4. yeah that's correct. ESC is disabling free look. ESC never used to effect free look mode. numpad+ and - in old versions did disable free look. but it would give you your mouse back. now you have to click mouse2 in vewport twice to get mouse back.(bug) i was also wondering if this can be changed so that pressing numpad +/- would keep you in free look. it should resolve the bug to
  5. i am noticing some laggy brush editing updates in 3d viewport. its not overly bad, but its only been introduced in recent builds when in 3d free look mode. hitting esc will disable free mode, not deselecting the brush. only mouse 2 should toggle view? also when in free look, if i change the speed with num_plus num_minus, it will toggle the free look mode. but not show mouse cursor. can this be set to not change free look modes. cheers dave
  6. i seem to be having an issue rendering alphatested shaders not sure if its a bug or my pc. old version seems the same 1. start editor fresh in fullbright texture mode. make a room. any normal texture. make another box alphatested eg.. textures/darkmod/metal/grate/trans_grating01 add light to cover whole room you will notice the alphatest area is black 2. change view to render lighting view. alphatest appears but the shader is translucent. 3. return to fullbright texture mode. the alpha test is working as it should
  7. have you tested gtk radiant/netradiant yet. how is the objects rendering in that? darkmod is a mod to doom 3. so most of its features are suported in gtk instead of doing evry shader you could set up something in the parseBlendType blendFuncFromStrings to return null. no image/blends do you know what stage types are causing the issue, like alpha blends, gl_one etc.. another area u can change parseShaderFlags if (token == "tranZlucent")
  8. should this issue go on the bug tracker. if you use 'load in textures view' from media browser, you cant see the new shaders in the texture browser until you click 'hide unused', then clicking it again. greebo was working on this as part of another improvement that's in the works.
  9. i'm not firmiluar with blender. but do you have an option to disable vertex normal on export. you could try that. i use max. and have found its corrupting the normal's on export if the model was not split at smoothgroups might be an issue on darkrad making normals to? check the cords of each normal in notepad. *MESH_VERTEXNORMAL 5 1.0000 0.0000 0.0000 you could manually try to remove the normals from exported ase. open the .ase in notepad, delet everything related.. *MESH_NORMALS { *mesh..... }
  10. i didnt notice this comment before. this is not the same issue i get , seems like a lynix/driver issue. wonder how many lynix versions have been downloaded without the same issue? they have made a big move to msv 2013 and wx. your os is probly the last thing on the dev's mind. if old versions work, use them.. or like ppl sugest. get windows. dual boot/emulator etc if u want to map for now, untill its looked into? check console to see if its useing the on board intel? maybe try another video card, geforce? a gfx tweaker? if you can build the git, then try rename a common shader atribute that is causing the issue eg. areaportal, translucent report your finds. it may help you and there development
  11. you still have not made a workaround?? what about editing the shaders, renaming translucent? noetpad++ will rename all of then files with find/replace
  12. the problen is that the barrel has a collision textures. you are selecting that you must have collision filter enabled. filters mite not work on parts of map models
  13. i have noticed some issue with the 'select group parts' toolbar button if i use the clipper tool (X). it deactivates the function, but the button is still enabled im not sure what the default method is ment to be, but if i did a edge (E) move on one of those bruses it disables group selection( the button disables corectly to) leaving 'select group parts' enabled with (E) (X) (V) might be a good oprion?
  14. another thing i noticed. there no more tool tips in the entity window.
  15. i added a file that u can try find, any of the 2 brushes ontop of 1 another replace, the individual brush have it as an option, to switch between both modes, if you do decide to impliment a second, is a bit of an exaggeration, it seems to be the same on a big map and a new map speed i can click at in std view is about 0.06 seconds speed i can click in freelook is about 0.23 seconds crash dump, i think its right? it seems to crash when i start draging the patch and its edge hits 512 grid units
×
×
  • Create New...