Jump to content

Didz

Members
  • Posts

    259
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Modding Interests
    Coder
    Jack of all Trades

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Didz's Achievements

  1. Do you want more control over how your weather behaves in your map, and bored of fx_rain, fx_snow, and fx_spacedust? This tutorial details a little secret unintentional "feature" of fx_runner that allows you to expose non-default weather effects. How does it work? Fx_runners with fxFiles beginning with '*' are treated as weather commands. (Most of these work in SP and MP!) Having acid rain for your multiplayer map is as easy as making an fx_runner anywhere on the map with the fxfile "*acidrain". It will rain acid upon your outside zones (or global if the map doesn't have zones) (Pain effects not included). Here's the list of all possible values you can use for weather: *acidrain // Adds a layer of acidic rain to the world (doesn't have pain effect in MP!) *clear // Clears current weather effects *constantwind ( VelX VelY VelZ ) // Adds constant wind to the world with the given XYZ velocity *die // Restarts the weather system *fog // Adds a layer of medium fog to the world *freeze // Freezes the weather particles on-screen *gustingwind // Adds gusting wind to the world *heavyrain // Adds a layer of heavy rain to the world *heavyrainfog // Adds a layer of heavy fog to the world *light_fog // Adds a layer of light fog to the world *lightrain // Adds a layer of light rain to the world *outsidepain // Toggles pain effect on (No effect in MP) *outsideshake // Toggles camera shake on (No effect in MP) *rain // Adds a layer of medium rain to the world *sand // Adds a layer of sandy fog to the world (looks ugly!) *snow // Adds a layer of falling snow to the world *spacedust AMOUNT // Adds a layer of immobile "space dust" to the world, AMOUNT specifies how dense it is (1000+ is best. Add wind effects if you want it to move!) *wind // Adds generic wind to the world *windzone ( MinX MinY MinZ ) ( MaxX MaxY MaxZ ) ( VelX VelY VelZ ) // Defines a cuboid wind zone with the given XYZ velocity (Doesn't exist in MP!) *zone ( MinX MinY MinZ ) ( MaxX MaxY MaxZ ) // Defines a cuboid weather zone (doesn't really make sense without inside/outside zones already compiled into the map) Colour Key: Utility - These commands exist mostly for testing and utility purposes. It doesn't make sense to use these in fx_runner because they don't do anything noticable when the map is loaded. Layers - These commands add particle effects to the world, up to 5 weather "layers" can be used in a map Wind - These commands add wind effects, they will move weather "layers" around, and up to 10 wind effects can be used in a map The spaces in the commands are VERY important, they will not work if the spaces aren't exactly how they are. This includes spaces between round brackets! These commands can be tested in-game directly in the console when cheats are enabled. Example: /r_we heavyrainfog. Here are some examples: (Each of the lines are different fx_runner entities in a map showing the value of the fxFile field) Typical Rainy Weather *rain *fog *constantwind ( 100 100 -100 ) Floating Snow *constantwind ( 0 0 350 ) *snow *light_fog Hydrochloric Acid *acidrain *acidrain *acidrain *acidrain *acidrain Typical Outside-Voyaging-Space-Station Weather *spacedust 10000 *constantwind ( 500 0 0 ) *light_fog Poopstorm *sand *gustingwind I hope this tutorial comes in handy for anyone! - Didz TODO: Screenshots of example entities in Radiant, and in-game result.
  2. Do you want more control over how your weather behaves in your map, and bored of fx_rain, fx_snow, and fx_spacedust? This tutorial details a little secret unintentional "feature" of fx_runner that allows you to expose non-default weather effects. How does it work? Fx_runners with fxFiles beginning with '*' are treated as weather commands. (Most of these work in SP and MP!) Having acid rain for your multiplayer map is as easy as making an fx_runner anywhere on the map with the fxfile "*acidrain". It will rain acid upon your outside zones (or global if the map doesn't have zones) (Pain effects not included). Here's the list of all possible values you can use for weather: *acidrain // Adds a layer of acidic rain to the world (doesn't have pain effect in MP!)*clear // Clears current weather effects*constantwind ( VelX VelY VelZ ) // Adds constant wind to the world with the given XYZ velocity*die // Restarts the weather system*fog // Adds a layer of medium fog to the world*freeze // Freezes the weather particles on-screen*gustingwind // Adds gusting wind to the world*heavyrain // Adds a layer of heavy rain to the world*heavyrainfog // Adds a layer of heavy fog to the world*light_fog // Adds a layer of light fog to the world*lightrain // Adds a layer of light rain to the world*outsidepain // Toggles pain effect on (No effect in MP)*outsideshake // Toggles camera shake on (No effect in MP)*rain // Adds a layer of medium rain to the world*sand // Adds a layer of sandy fog to the world (looks ugly!)*snow // Adds a layer of falling snow to the world*spacedust AMOUNT // Adds a layer of immobile "space dust" to the world, AMOUNT specifies how dense it is (1000+ is best. Add wind effects if you want it to move!)*wind // Adds generic wind to the world*windzone ( MinX MinY MinZ ) ( MaxX MaxY MaxZ ) ( VelX VelY VelZ ) // Defines a cuboid wind zone with the given XYZ velocity (Doesn't exist in MP!)*zone ( MinX MinY MinZ ) ( MaxX MaxY MaxZ ) // Defines a cuboid weather zone (doesn't really make sense without inside/outside zones already compiled into the map)Colour Key:Utility - These commands exist mostly for testing and utility purposes. It doesn't make sense to use these in fx_runner because they don't do anything noticable when the map is loaded.Layers - These commands add particle effects to the world, up to 5 weather "layers" can be used in a mapWind - These commands add wind effects, they will move weather "layers" around, and up to 10 wind effects can be used in a mapThe spaces in the commands are VERY important, they will not work if the spaces aren't exactly how they are. This includes spaces between round brackets! These commands can be tested in-game directly in the console when cheats are enabled. Example: /r_we heavyrainfog. Here are some examples: (Each of the lines are different fx_runner entities in a map showing the value of the fxFile field) Typical Rainy Weather *rain *fog *constantwind ( 100 100 -100 )Floating Snow *constantwind ( 0 0 350 ) *snow *light_fogHydrochloric Acid *acidrain *acidrain *acidrain *acidrain *acidrainTypical Outside-Voyaging-Space-Station Weather *spacedust 10000 *constantwind ( 500 0 0 ) *light_fogPoopstorm *sand *gustingwindI hope this tutorial comes in handy for anyone!- Didz TODO: Screenshots of example entities in Radiant, and in-game result.
  3. Have you tried it with jampded.exe instead of jamp.exe? I don't know if Makermod runs in jamp.exe by default because it has engine hooks built in that require the dedicated server exe instead (though I don't know if these are now automatically disabled when not running in the dedicated server).
  4. I'm also going to join the unanimous disagreement here to say that this sounds like a solution looking for a problem. I don't think it's wise to have a launcher compiling code for the end-user as an excuse for the developer not to have tested their code on their target platforms. Compilation is always tricky, so spreading the requirement of compilation over multitudes of end users seems quite silly when you know that the package the developer builds will always be proper.
  5. I believe it'll be the same packages and command line as for CentOS: https://github.com/JACoders/OpenJK/wiki/Compilation-guide#centos-7-for-dedicated-server-and-mp-libraries Or possibly it could be libjpeg-turbo-devel? https://www.rpmfind.net/linux/rpm2html/search.php?query=libjpeg-devel(x86-64)
  6. 244 downloads

    Description: Relive the old Windows 1.0 days with a Fixedsys console font! Replaces the font used in the console, game timer, chat prompt and FPS meter Supports all characters in the Windows-1252 encoding Installation: Open the zip archive and extract the pk3 file to your GameData\Base folder. You can usually find this under "C:\Program Files (x86)\LucasArts" on Windows.
  7. Didz

    OpenJK Changelog

    I can remember the small stuff I pushed: Raw mouse input support (maybe SDL handles this now, I'm not sure)Game window without borderGame window centeringImproved some multi-monitor issues on Windows (where vid_restart would cause the game to jump to another screen)MP configurable console transparency to match SPConsole version number now 8 pixels to the left
  8. Didz

    seamless portals

    I got portals rendering on quads and that's about as far as I think I got: It had trouble rendering multiple portals at once and recursive portals, so it was basically with the same limitations as basejka misc_portal entities. The engine source code wasn't out at this point but in the Q3 source code I believe there's a single if statement that limits how many portals can be rendered at once to 1 (which also prevents recursion). This rendering experiment wasn't done with the portalmod source code, so there was no moving through portals here. Also I wasn't sure how I'd fix issues like this, where the result of one portal renders through another: In the 21st century, you'd probably do this with stencil buffers to limit the rendering of each portal to within their "viewport". Maybe this already happens and there needs to be multiple "levels" of stencil to handle distinct portals.
  9. HTTPS is now enabled and enforced on https://builds.openjk.org :D If anyone has any problems connecting, please let me know! (Unfortunately, Android 2.3 and Windows XP's Internet Explorer aren't supported)

    1. Archangel35757

      Archangel35757

      Firefox 44 works for XP.

  10. One year without downtime is not bad I guess
  11. You do not need to open port 29060 on your server. The master server listens on that port, but it communicates with your server on whichever port your server is listening on (sending heartbeats from). If players can connect, your ports are all fine and the master server should be able to contact it. For anyone else finding this post by searching, make sure you have opened UDP port 29070 (or whatever you've set your net_port cvar to) incoming. TCP is not required. If your server is not sending heartbeats, then you haven't set the 'dedicated' cvar to '2' or your sv_masterX cvars are not set. These are the only reasons that heartbeats wouldn't be sent.
  12. It's been a while since doing BSP modding, but I remember having this issue sometimes too. I think all that I had to do was move the sub BSP instance to somewhere else in the level. Try adding or removing zeroes to the end of the BSP's origin. This may actually be an issue that relates to the size of the sub BSP too. I vaguely remember the derpiness in larger maps when you're relatively far away from their origin, whereas simple ones like t1_inter would work fine.
  13. What I mean was convert misc_model_breakable to misc_model_static. misc_model are indeed converted directly to brushes and so won't count against the entity count. misc_model_static are client-side entities that get loaded at runtime and won't contribute to the server's entity count either.
  14. This simply means you have too many entities in your map. There's a limit of 1024. If this is because you have loads of misc_model_breakable entities, you'll need to change them to misc_model or misc_model_static since those don't count towards the entity count. These would require clipping brushes made for them for collision, since they're not entities on the server-side. You may also be using dynamic lights in your map instead of the normal light entities. Make sure you only use 'light' entities where the lights are just static - the others will take up entity space.
×
×
  • Create New...