Jump to content


JKHub Staff
  • Content Count

  • Joined

  • Last visited

About AshuraDX

  • Rank
    JKHub Staff

Profile Information

  • Gender
  • Location
  • Interests
    3d Modeling , Parkour/Freerunning
  • Modding Interests
    Texture Artist

Contact Methods

  • Steam
  • Discord
    ashuradx #1192

Recent Profile Visitors

10,177 profile views
  1. Or selecting a single brush and pressing g will also select all other brushes in the same entity
  2. @quakefreed You could also create a shortcut to jasp.exe and add the startup parameter +devmap <mapname> To the path in there. That should also work. HowTo: https://www.digitalcitizen.life/shortcut-arguments-parameters-windows/ The tutorial uses -, for jka console commands use + instead. @NAB622 autoexec.cfg should automatically be run by the game, you shouldn't need to tell it to run it on launch.
  3. Huh, that is odd - one thing you could try is using vid_restart before loading your map again. AFAIK that reloads all .shader files and other assets as well.
  4. Not a fan of the overlayed high contrast grunge. It darkens the texture considerably and makes it look rather dirty. I'd try a more subtle approach, add small chips and scratches here and there. Maybe some light Dust Buildup. Or you could try the cheapo route and apply a high pass filter to the grunge map with a low radius. If done correctly you will get Something that sort of resembles a curvature map for your grunge and could overlay that. This would give the crisp details from the grunge, without massively changing the colour of the underlying texture. Example:
  5. @fullkevlar would you like me to update the roff to match the new positions or would you prefer having me send you a new file with just the start and end points in it? As long as the difference between those two points match what's in the roff, it's all gonna be fine and matching.
  6. My mapping Toolkit for 3ds max, Q3ME, includes a roff exporter. I was planning on walking someone through using it on stream and make that stream available on Youtube, then release the current version of Q3ME (which is long overdue). @mjtcould guide you through the process in blender. Oh dear, that's some bad luck. Hope you get it fixed soon! Happy new year to you too, let's hope that burst pipe is 2020's last swipe your way 😄
  7. @fullkevlar The base animation for the roff, already have it ingame but I sadly ran out of time to record a video of it right now. (After I spent hours looking for the cause of a problem that ended up being a typo in a ref_tags targetname.... don't mod when you've been awake for more than 20 hours peeps.) But here's a pk3 file for you (and everyone else interested) to try ingame and dissect, to see how it was done. Just load the map and press the use button (you spawn inside a trigger_multiple). The animation can be repeated as often as you'd like, there's a 10 second wait on th
  8. that's quite choppy @fullkevlar can you send me a .map file with the ref_tags you used to move the model? I just need their coordinates actually and the starting coordinates of the object you're moving
  9. I'd suggest using a more unique name than just "singleplayer.shader" for any project. If people combine pk3 files from multiple mods you don't want your shader to be overwritten. Try adding a unique identifier to your shader file names, something like "fkv", based on your username, as pre-/suffix. I often use "<name>_adx.shader" Shadered2 makes some parts of shader creation easier, but it does not support all of the parms we can use on our shaders.
  10. Radiant 1.5 never ran on windows 10 for me, 1.6 worked quite well
  11. Yeah, switching to Radiant 1.6. Should help. I found working in that far more bearable than trieing to use 1.4 on Windows 10
  12. @fullkevlar iirc there is a menu to do that in somewhere in the gtk Radiant Preferences, alternately you could edit the file you edited to fix your q3map2 problem. Or you write a bat file to compile your map with. Which is what I do from my (still unreleased) Q3ME.
  13. @fullkevlar You might want to use '-bouncegrid' in your light compile, your map looks like it relies heavily on bounced lighting to light up the corridors and by default this does not affect the lightgrid afaik. '-bouncegrid' should take care of that. I also think I remember reading that using -fast can screw with the lightgrid, and there was a workaround to that, or rather a way to compile without using fast without sacrificing a lot of speed. Didn't you dig that up @mjt
  14. @fullkevlar use find and replace: Search for: /q3map2/q3map2/ Replace with /q3map2/ Repeat until it finds no more occurances
  15. Hey, how/in what way is the map corrupted? Just the bsp output after compiling or the .map you edit in Radiant?
  • Create New...