ZX 707 has contributed to 113 posts out of 468958 total posts
(.02%) in 2,656 days (.04 posts per day).
20 Most recent posts:
OS shaders are just extensions of normal ones. At the bottom of the model tag you can see what type of shader it was. Only shader_model and shader_environment have OS extensions so you would only have to recreate those.
Open debug.txt (located in the same folder as sapien) and copy and paste the last entry here.
It should look something like below except with your errors:
04.26.16 13:56:18 sapien pc 01.00.00.0609 ----------------------------------------------
04.26.16 13:56:18 reference function: _write_to_error_file
04.26.16 13:56:18 reference address: 401b13
04.26.16 13:56:18 Couldn't read map file './sapienbeta.map'
04.26.16 13:56:20 CreateDevice succeeded with refresh rate = 0
04.26.16 13:56:21 Increasing sound decompression buffer size to 1048576 bytes
04.26.16 13:57:03 local player 0, weapon (0x0), deleted unexpectedly
You would have to recompile the map with the weapons you want in it.
To change the starting weapons, you would have to create an item_collection tag for your weapon and then change the "starting equipment" section of the scenario tag for the gametype you want. For singleplayer, the gametype is "none".
Quote: --- Original message by: jabukufo
Or maybe a way to switch the assault rifle tags with a custom weapon tag so that choosing picking up an AR on ANY map whether it's a multiplayer or campaign map would put a BR in your hand?
This will not work. The weapon tags are separate for each map.
Separate the bitmaps vertically and surround them by at least 1 pure blue (0,0,255) pixel. Run in tool and change the bitmap type to sprites, then rerun tool.
Different passwords for different versions
You can make it darker by changing the indoor and outdoor ambient radiosity power and color at the top of the sky tag.
Quote: --- Original message by: DoodleSama
But it's not an opinion that 60FPS is better than 30FPS. It is a FACT. A word that most people on Halomaps can't tell the difference of what is a fact and an opinion. That's why I called Masterz a retard and rightfully so.
An opinion is a personal belief or view. "Like," "enjoy" and "hate" are objective words that form an opinion. Thus what Masterz said and what you said are opinions. You like 60fps, Masterz likes 30fps, both opinions.
You even called what Masterz said an opinion:
Quote: --- Original message by: DoodleSama
Just get out of video games. That is the dumbest opinion I have ever heard from you.
Make sure in guerilla that everything AI is deleted including encounters and command lists. Also delete cutscene flags, cutscene titles and camera points.
You also need to delete the scripts/globals as well. You can't do this in normal guerilla so either use OS_guerilla or compile a blank script file in sapien.
Since this is for multiplayer did you place spawn points/netgame flags for CTF or whatever mode you want to be able to play in? Make sure your setting the team index to 0 for red and 1 for blue.
Also, did and set up "starting equipment" for all games (select in the drop down box) and delete the "player starting profile" section in guerilla?
First, you don't open map files with sapien, you open scenario tags.
Default CE does not come with the single player tags. You can get these you can get them by downloading them from the site or rip them with HEK+. Ripping them can cause some issues with tags getting corrupted.
Download Tags: http://hce.halomaps.org/index.cfm?fid=6690
If you are going to change the scripts then you will need the zteam scripts: http://hce.halomaps.org/index.cfm?fid=3424
Open Sauce is not the only way to open single player scenarios. Unless your using the features OS gives you like shader extensions, script extensions, DLMs, boarding or actor transformations, you don't need OS. Normal sapien works just fine.
Also, the newest OS is here: https://bitbucket.org/KornnerStudios/opensauce-release/downloads
In the core CMT TSCE tag release there is a scenario called range_test. It has all the materials as part of the bsp. Most of the shaders use default tagset bitmaps as well.
Here is a video of it (except for the water): https://www.youtube.com/watch?v=mXGrTmMEexs
You will have to delete some tags in the scenario and remove the scripts if you want to use it without OS though. Or you could just make a new scenario tag and reference the bsp.
In the weapon tag at the bottom find the firing damage .damage_effect
In that tag change "permanent camera impulse" to some value such as -0.5
Did you type radiosity_save when it finished?
Open the equipment tag and switch the grenade type at the bottom to "custom 2" or "custom 3" to match what you have in the globals tag.
Quote: --- Original message by: sparky
The HEK+ WILL NOT EXTRACT TAGS FROM Halo Custom Edition map files.
HEK+ does extract from Custom Edition Map files. It's the reason why people tried to protect maps.
You don't need to use the symbols for scenery/biped/vehicle models. The are only used for bsp and collision models.
Double sided can be done by checking a box in the shader_trasparent_chicago tag you are using and transparency can be changed by blending options in the tag or by altering your bitmap's alpha channel.
Have you tried http://hce.halomaps.org/index.cfm?fid=3627 ?
There are two scripts. The compact version worked for me in Max 2012.
You can get all the campaign scripts here: http://hce.halomaps.org/index.cfm?fid=3424
Zteam tags use different 3p animations for many of their weapons. You need to use the zteam biped animations. You can also change the weapon label in the weapon tag to something in the default cyborg.model_animations such as hp, ar, sg, sr, pr and so on.
You can't use 2x2 because when compressing with color-key transparency it takes a 4x4 block of pixels to compress. I just use 4x4 and it works perfectly.