Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Sign in to follow this  
Guest Mauler

TT Custom Scripts.dll

Recommended Posts

If you have the readme txt file you should post that as well. If not I have it and can post it later. I prefer the readme because it has them all listed and you can search it for keywords like buy or purchase to find a script you need.

Share this post


Link to post
Share on other sites
Guest Mauler

If you have the readme txt file you should post that as well. If not I have it and can post it later. I prefer the readme because it has them all listed and you can search it for keywords like buy or purchase to find a script you need.

 

post the file up and i will get it posted here in a nice format...

Share this post


Link to post
Share on other sites

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.   Restore formatting

  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.

Loading...
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By zunnie
      This package contains everything you need to get a server going.
      When you downloaded the zip file make sure that you goto its properties and "Unblock" it BEFORE you extract the files, else it may not function correctly.
       
      There is a folder called "prerequisites" and you must run and install the vcredist_x86_2012.exe and vcredist_x86_2013.exe and also the dxsetup.exe found in the dxsetup folder or your server will not run.
       
      Make sure you edit server.ini and change ports where needed and forward them if applicable. Note that the GameSpyQueryPort *must* be different from what you set in DA.ini
      Also edit the svrcfg_cnc.ini found in the data folder to set your own server name, title, and maybe some other options.
       
      Brenbot is included in this zip and works 'out of the box' pretty much.
      You should however change the nickname of the bot to use on IRC, the channels it will join and the Path to your Server root folder.
      See moderators.cfg for help adding moderators.
      The FIRST message listed in messages.cfg is what will be displayed when players type !rules in your server. Keep it very short as there is a ~200 character limit on lines.
       
      I've included an example configuration of the tt.cfg file that now handles the server map rotation and downloader properties.
      It's pretty straigthforward, just upload your ttfs folder to your website and set the repositoryUrl to it ending with a /
      eg: repositoryUrl = "http://www.yourwebsite.com/ttfs/";
      A note: When you use the packageeditor cmdline to install or convert new maps or packages make sure the Server is NOT running.
       
      If you've adjusted your configuration files and are ready to run it, then execute the file server.exe followed by brenbot.exe
      Always start the server first, then brenbot.
       
      The sourcecode based on Dragonade 1.92 with TT 4.6 support is included and contains a nice mpf_example to get going.
      You need both Visual Studio 2012 and Visual Studio 2015 installed. You can get VS2015 Community Edition off Microsoft's website. However, there is no community edition for VS2012.
       
      For help adding custom maps and/or other things to your server please join us on our irc.cncirc.net in channel #mpf
      It is recommended to join us on Discord with a microphone as it is a lot easier to help then. Perhaps also get Teamviewer, we use that a lot and makes it tenfold easier to help remotely with issues you may have. ( www.teamviewer.com )
    • By zunnie
      - Introduction -
      To run a Renegade Dedicated Server you need to install the Renegade FDS (Renegade Free Dedicated Server).
      A dedicated server is basically a command prompt type program which allows for Renegade Clients to connect
      and play on the server. Dedicated servers are usually unattended and you cannot play as the host while running
      a dedicated server. Running a dedicated server also enables you to run SSGM 4.0 and/or other special modifications
      which are unavailable for the game client.
       
      - MPF Public FDS Package -
      You can now download a prepared package of the FDS with DA 1.92 and TT 4.6 applied, source code included with examples @



      - Downloads -
      You can download the RenegadeFDS installation file on for example multiplayerforums over here:
      http://multiplayerforums.com/index.php?/files/file/8-renegade-fds-1037zip/


      - Installation -
      After you have installed the Renegade FDS, copy the contents of the serverfiles folder from the 4.0 server download into the FDS folder.
      Edit server.ini, svrcfg_cnc.ini, tt.cfg and ssgm.ini as per the documentation in this topic.
      You then also need to install the Visual C++ runtime libraries and the DirectX runtimes from the "redist" folder.
      The server.exe file in the 4.1 server download is the one you should be using as it has been modified.
      You do not need to apply the "no gameplay pending" patch to it as that patch is now a server.ini option.
      Make sure anticheat.ini is in the data folder otherwise the anti-cheat will probably kick you even with stock renegade files.


      - Requirements -
      When running the server in Westwood Online Mode (or XWIS these days) you require a valid serial number to run the server.
      This can be a FDS Serial or your Renegade Client serial.
      In GameSpy mode there are no requirements.


      - Notes for WOL Mode (XWIS) -
      To get passed the WOL installation for the RenegadeFDS you need to enter a (fake) serial number that starts with 0669.
      For example: 0669714956637887900319 ( Note: This is a fake serial and you cannot host a server in XWIS/WOL mode with this serial,
      it is only provided for you so you can get passed the installation dialogs. )
    • By Generalcamo
      Originally Posted by Jonwil, ported to the new RenHelp by Generalcamo, with additional information added.
       
      Firstly, a bug has been identified in the vertex solve code related to meshes with bump mapping such as water. With the fixes provided by 4.0, you no longer need to hide water meshes before you run "compute vertex solve".
      Secondly, another bug was identified whereby meshes that have no vertex colors and have an opacity of less than 1 set in their material settings would be treated as though the opacity was set to 1. This has been fixed
      The most well known example where the opacity bug can be seen is with the glass in the nod airstrip tower. With the new fixes, you will no longer need to hide any of the glass on the stock renegade buildings (including the air tower and the hand of nod) before you run "compute vertex solve".
      Thirdly, 4.0 adds a new feature to the vertex solve code that lets you completely disable vertex solve on a particular mesh. This is intended for meshes where the vertex solve still screws up even with the above 2 features as well as for vertexes that contain pre-calculated lighting baked into the w3d file. (such as lightmap textures) To use it, you select the mesh in 3DS MAX and open the "Properties" dialog. Then you click on the "User Defined" tab. In that box you type "Prelit=true" (without the quotes). This will cause the vertex solve code to completly ignore this mesh (i.e. its essentially same as hiding the mesh before you vertex solve) The process is similar in Gmax/RenX.
       
      NOTE: If you are using the Prelit=true feature on a mesh that is part of anything other than terrain, ALL the meshes in that w3d file need to be Prelit=true otherwise it will screw up when you run the vertex solve.
       
      Before we go into some of the deeper and more complicated stuff, here is some information about w3d you might need to know:
      1.Buildings have a prefix set in the building definition
      2.Meshes that contain the building prefix followed by the ^ character are exterior meshes for that building
      3.Meshes that contain the building preset followed by the # character are interior meshes for that building
      4.Buildings can also have lights associated with them. Lights will match the building if the name of the light (which is taken from the .wlt file, see below) matches with the mesh prefix of the building.
      5.Lights in renegade can come from 2 places, they can be directly placed into leveledit or they can be placed via a .wlt file
      6.Every light in renegade has a "group ID" and a name.
      7.A .wlt file is a file that is associated with a terrain .w3d file and contains one or more groups of lights.
      8.When a .wlt file is loaded into leveledit, the lights are given names matching the .wlt filename.
      9.The first group of lights in the .wlt file are given a "group ID" of 0, the second group is given a "group ID" of 1 and so on.
      10.When a building is initialized, it creates 4 lists (actually 5 if you count the building aggregates but that doesn't matter for this discussion) and fills them with the appropriate data. The InteriorMeshes list contains all the interior meshes for the building. The ExteriorMeshes list contains all the exterior meshes for the building. The PowerOffLights list contains all the lights with a name that matches the building and a "Group ID" of 1. The PowerOnLights list contains all the lights with a name that matches the building and a "Group ID" of 0.
      10.Meshes can have "Alternate materials" associated with them. This is basically a second set of material data stored in the .w3d file. (this second set of data may contain textures, shader settings, material settings, texture coordinates etc)
      11.When a building is destroyed, the alternate materials on both the interior and exterior meshes are enabled. When a building goes low power, the alternate materials on the interior meshes are enabled.
      14.When a building is destroyed or goes low power, all the lights in the PowerOnLights list are disabled and all the lights in the PowerOffLights list are enabled.
       
       
      With these fixes, we have also identified how to make Alternate materials and alternate lighting work. The alternate material feature will only work properly on terrain and will only work on meshes that are prelit (i.e. those that have "Prelit=true" set)
      The alternate lighting feature will only work properly if the meshes being lit all have Prelit=true set. Meshes which do not have Prelit=true (and therefore get lighting from the vertex solve) will probably not look correct when the lights switch to the "power off/dead" set of lights.
      To use the alternate lighting feature you do the following: (there may be other ways to generate .wlt files, I am only describing the way I know to do it)
      1.Load leveledit and create a blank map
      2.Place the building interior terrain for the building you want to add lights to at 0,0,0 (i.e. so that 0,0,0 in the building terrain is at 0,0,0 in the level)
      3.Create any light presets you like and place them anywhere in the level (but presumably they will be inside the building). These will be the "normal" lights
      4.Choose Lighting-Export... from the menu. Save the lights as e.g. normal.wlt (the name doesn't matter, I am using normal.wlt for this example)
      5.You can (if you like) save this level with the placed lights in it for later further work if you like (you dont need to though)
      6.Delete all your "normal" lights
      7.Place your "dead" lights (which will also be used when there is low power)
      8.Choose Lighting-Export... from the menu. Save the lights as e.g. dead.wlt (the name doesn't matter, I am using dead.wlt for this example)
      9.You can (if you like) save this level with the placed lights in it for later further work if you like (you dont need to though)
      10.Put wltmake.exe, memorymanager.dll, normal.wlt and dead.wlt in a folder. Open a command prompt and go to this folder.
      11.Run wltmake out.wlt normal.wlt dead.wlt. Instead of out.wlt in that command, use the name of your building interior mesh but with a .wlt extension (so if the building is mabar_int.w3d, the wlt file would be mabar_int.wlt)
      12.Copy the new output wlt file into your always.dat file or whatever (somewhere LE and the game can find it)
      13.Edit the preset for your building interior terrain and set m_LightFilename to the name of your new .wlt file
      14.Repeat steps #1 to #13 for all the buildings that need special lights
      15.Once that is complete, open up each map that contains the newly-lit buildings.
      16.Delete any instances of the building interior meshes (or of any terrain that proxies them in) and re-insert them into the level so that the lights get pulled in.
      17.Save and re-export the map.
      18.Enjoy your new lighting (hopefully)
      To use the alternate materials feature you do the following:
      1.Take your mesh in max or gmax and apply the "normal/alive" materials (including any light maps you may have created)
      2.Export this to a w3d file (lets call it normal.w3d for this example)
      3.Edit the mesh and apply the "dead" materials (including any light maps you may have created)
      4.Export this to another w3d file (lets call it dead.w3d for this example)
      5.Put both w3d files, memorymanager.dll, altmat.exe and w3dlib.dll in a folder. Open a command prompt and go to this folder.
      6.Run altmat out.w3d normal.w3d dead.w3d replacing out.w3d with the name of the output mesh you want (i.e. the name that matches the building you are working with)
      7.Place the new w3d file in a place that leveledit and the game will find it.
      8.Export your maps as normal
      9.Load the game and enjoy your new materials
      The things you can change between normal and dead materials are:
      Vertex colors
      Texture coordinates
      All the values on the Vertex Material tab
      All the values on the Shader tab
      All the values on the Texture tab EXCEPT for the "Stage 0 Texture" and "Stage 1 Texture" checkboxes
      Changing anything else (including geometry or pass counts) will not work and may lead to crashes (in altmat or in the game).
      Remember that you can't rename a w3d file so make sure you use the correct output filename.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.