FreeSpace Wiki - User contributions [en]

Sample Lighting Settings

2012-07-29T07:32:17Z

Karajorma: /* Recommended "Baseline" Settings */

This page documents some sample lighting settings. These must be entered into the optional command line parameters to have any effect. Best results are always achieved using the MediaVPs and with glowmaps, shinemaps, normal maps and environment maps turned on. Please consult the [[Command-Line Reference#Lighting|Command Line Reference]] page for specific notes on these settings.

==FreeSpace Engine Default Settings==
These are the Engine defaults used when no settings are specified as shown [[Command-Line_Reference#Lighting|here]], for easy reference.
*-ambient_factor 128
*-spec_exp 16
*-spec_point 1.0
*-spec_static 1.0
*-spec_tube 1.0
*-ogl_spec 80
*-bloom_intensity 75

==Recommended Diaspora Settings==
These are the recommended light settings for Diaspora. For now, you'll only see them available in Diaspora's version of the launcher.
* -ambient_factor 90
* -spec_exp 0.7
* -spec_point 0.7
* -spec_static 1.0
* -spec_tube 1.0
* -ogl_spec 15
* -bloom_intensity 20

{{note|Copy and paste this line into your launcher's custom flags box to make it work: -ambient_factor 90 -spec_exp 0.7 -spec_tube 1.0 -spec_point 0.7 -spec_static 1.0 -ogl_spec 15 -bloom_intensity 20}}

==Recommended "Baseline" Settings==
These are the recommended light settings as mentioned [[Command-Line_Reference#Lighting|here]], for easy reference.
* -ambient_factor 75
* -spec_exp 11
* -spec_point 0.6
* -spec_static 0.8
* -spec_tube 0.4
* -ogl_spec 60

{{note|Copy and paste this line into your launcher's custom flags box to make it work: -ambient_factor 75 -spec_exp 11 -spec_point 0.6 -spec_static 0.8 -spec_tube 0.4 -ogl_spec 60}}

==DaBrain's Settings==
[[Image:Lighting-db1.jpg|thumb|DaBrain's settings feature relatively even lighting with a low specular value.]]
*-ambient_factor 10
*-no_emissive_light
*-spec_exp 7.0
*-spec_point 8.6
*-spec_static 12.8
*-spec_tube 5.0

{{note|Copy and paste this line into your launcher's custom flags box to make it work: -ambient_factor 10 -no_emissive_light -spec_exp 7.0 -spec_point 8.6 -spec_static 12.8 -spec_tube 5.0}}

==Herra Tohtori's Settings==
[[Image:Lighting-herra.jpg|thumb|Herra Tohtori's settings feature high specularity and glossiness.]]
*-ambient_factor 35
*-no_emissive_light
*-spec_exp 15
*-spec_point 1.2
*-spec_static 1.5
*-spec_tube 1.5
*-ogl_spec 20

{{note|Copy and paste this line into your launcher's custom flags box to make it work: -ambient_factor 35 -no_emissive_light -spec_exp 15 -spec_point 1.2 -spec_static 1.5 -spec_tube 1.5 -ogl_spec 20}}

==CKid's Settings==
[[Image:Lighting-ckid.jpg|thumb|CKid's settings adds emphasis on glowmaps and normal maps.]]
*-ambient_factor 35
*-no_emissive_light
*-spec_exp 16.7
*-spec_point 0.6
*-spec_static 0.9
*-spec_tube 1

{{note|Copy and paste this line into your launcher's custom flags box to make it work: -ambient_factor 35 -no_emissive_light -spec_exp 16.7 -spec_point 0.6 -spec_static 0.9 -spec_tube 1}}

==ColeCampbell666's Settings==
[[Image:Lighting-cc666.jpg|thumb|ColeCampbell666's settings result in a very dark environment with most of the lighting coming from weapons fire.]]
*-ambient_factor 0
*-no_emissive_light
*-spec_exp 11
*-spec_point .6
*-spec_static .8
*-spec_tube .4
*-ogl_spec 80

{{note|Copy and paste this line into your launcher's custom flags box to make it work: -ambient_factor 0 -no_emissive_light -spec_exp 11 -spec_point .6 -spec_static .8 -spec_tube .4 -ogl_spec 80}}

==Castor's Settings==
[[Image:Lighting-castor.jpg|thumb|''"The thing with 'darker' settings is that the lower you go, the more dependent it will be on the quality/settings of the particular display you are viewing it on."'' -- Castor]]
*-ambient_factor 75
*-spec_exp 7.0
*-spec_point 8.6
*-spec_static 3.0
*-spec_tube 5.0

{{note|Copy and paste this line into your launcher's custom flags box to make it work: -ambient_factor 75 -spec_exp 7.0 -spec_point 8.6 -spec_static 3.0 -spec_tube 5.0}}

==Spidey's Settings==
[[Image:Lighting-spidey.jpg|thumb|Spidey's settings nicely balance emphasis on diffuse, specular, and normal maps.]]
*-ambient_factor 5
*-spec_exp 15
*-spec_point 1.2
*-spec_static 1.7
*-spec_tube 1.5
*-ogl_spec 50

{{note|Copy and paste this line into your launcher's custom flags box to make it work: -ambient_factor 5 -spec_exp 15 -spec_point 1.2 -spec_static 1.7 -spec_tube 1.5 -ogl_spec 50}}

==Woolie Wool's Settings==
[[Image:Lighting-woolie.png|thumb|Woolie Wool's settings use a very focused specular lighting to emphasize the normal maps and model contours, and a high ambient light setting to make lighting more dependent on the mission settings.]]
*-ambient_factor 105
*-no_emissive_light
*-spec_exp 9
*-spec_point 0.3
*-spec_static 0.8
*-spec_tube 0.7
*-ogl_spec 120

{{note|Copy and paste this line into your launcher's custom flags box to make it work: -ambient_factor 105 -no_emissive_light -spec_exp 9 -spec_point 0.3 -spec_static 0.8 -spec_tube 0.7 -ogl_spec 120}}

[[Category:Source Code Project]]

Variables

2009-01-10T10:50:02Z

Karajorma: /* Three Types of Variables */

'''Variables''', implemented in retail FS2, can be a powerful FRED tool. [[FREDder]]s use variables for the same two reasons that programmers do. One, they allow you to easily store pieces of information for later use, which can be modified and used to do cool things. Two, they let you avoid hard-coded or "magic" numbers for arguments that you use several times in your mission's events.

Using variables is simple. You can use variables in place of any SEXP argument where you would normally use a string or number. Right-click on the argument in the Events list and look at the three options at the bottom of the menu, '''Add Variable''', '''Modify Variable''', and '''Insert Variable'''. Click '''Add Variable''' to create a new variable. '''Modify Variable''' allows you to change a variable that you've already created. '''Insert Variable''' replaces the currently selected SEXP argument with the variable of your choice.

== Three Types of Variables ==

There are three types of variables.

'''Player-persistent:''' This type of persistent variable is stored in the pilot file. Further, they are stored immediately when they are created/changed from within a mission. This means that any change is going to be there regardless of the later outcome of the mission. Player-persistent variables can be accessed and changed from any campaign played with the same pilot.

'''Campaign-persistent:''' These persistent variables are stored in the campaign file, and are only stored when a campaign progresses to a new mission. So if the player is killed or quits during a mission, and changes made to a campaign-persistent variable are not stored.

'''Network variables''' are only relevant in a multiplayer game. Non-network variables are only ever altered on the server. This means that they can not be used in messages or scripting because all the client machines will only ever have the default value. If you need to have the value of a variable display in a message you will need to mark it as a network variable. ''

== Variables and Messages ==

Variables can also be used in messages. To do this, use the variable's name preceded by the '$' token (for example "$killcount"), and in-game this will be replaced with the value of the variable. It works for both numeric and string variables.

==Links==

*[http://homepage.ntlworld.com/karajorma/FAQ/fredretail.html#variables Karajorma's FreeSpace FAQ on variables]
* Fred Zone examples for variables [http://fredzone.hard-light.net/cetanu_adv-fred-lessons.shtml] [http://fredzone.hard-light.net/cetanu_adv-fred-lessons-2.shtml]

[[Category:FRED]]

Talk:Battle of Endor Syndrome

2008-06-20T22:30:41Z

Karajorma:

"Scheme" isn't really an appropriate wording for this subject - Black Wolf

What about "Disease"? Figuratively, I mean - TopAce

It's traditionally been called "Battle of Endor Syndrome" AFAIK. - Black Wolf

I did not want to use that title, I wanted a new one. - TopAce

Why? - Black Wolf

Only to differenciate the two articles. - TopAce

Article moved. - TopAce

I question the validity of this article in this day and age; most of the anti-BOE resources cite FS1 limitations. I can cite several campaigns that have had well-executed Endor-esque situations off the top of my head. If the mission fell apart it was for other reasons. I'll agree it's not for the novice FREDder, but unless and until you can properly execute a large mission, you haven't really earned your spurs.-ngtm1r

In my opinion, the modern-day objections about BOE missions can be boiled down to two points:
*The complexity of a BOE mission requires a very skilled FREDder to pull off effectively
*Because of scale, it is difficult or impossible for the player to affect the outcome of a BOE mission in any way, something that is usually desirable from a gameplay standpoint
I think these points adequately justify the continuing prejudice against these kinds of missions. This, of course, does not imply that it cannot be done, only that it is very difficult. I can cite the penultimate mission of Inferno as an excellent example of a BOE mission done right, IMHO. --[[User:Goober5000|Goober5000]]00:43, 1 January 2007 (CST)

Altered the article, and considering further alterations, considering that we're basically agreed upon that A: such missions are possible and B: it isn't technical limitations holding the game back from them anymore. --[[User:ngtm1r|ngtm1r]] 10:21, 2 October 2007 (PST)

Whether you consider it possible or not there have been many, many user-made campaigns featuring decent BoEs. The main reason for prejudice against them is that someone who didn't know how to use FRED tried to make one, then wrote a VolitionWatch article a long time ago about it. 'Bout time, nghtm1r, and thank you. [[User:Mustang19|Mustang19]] 13:39, 2 October 2007 (CDT)

As the person who wrote the Volition Watch article and had 2 missions on the Game of the Year edition, I disagree and removed the uninformed slur. Back at the creation of FS1, there were significant technical constraints and Volition programmers put limits into place to restrain their mission editors. The initial FRED discussion list (FDL) was concerned with how poorly designed missions were impacting user reaction to FreeSpace, and making the community difficult to gain respectability among all the trash missions that were released. That's why I worked with Peter Drake on explaining the initial FRED docs and pioneered a community peer-review system. While technology has advanced even in FreeSpace 2, such missions are not just difficult to appropriately test and balance (as those at Volition Watch who worked on Inferno were well aware). A well-crafted battle and story relies on specific set pieces, rather than just letting the AI simulation cover up the lack of design. It's not prejudice, it's a recognition of good design. - Zarathud 6/13/08 10:00 CT

Beg differ. It is ''extremely'' difficult for what you say to take place. A mission where it does will have bigger problems then this; indeed, a campaign where it does will have problems even in non-Endorish missions. As observed before as well, a well-crafted battle relies on suspension of disbelief just to get there; capitals moving and attacking in groups helps establish this. And more to the point, you are speaking from an FS1 sensablity in regards to not only mission design and technology, but also storytelling. In FreeSpace 1 it was much more acceptable for such things to occur. The Shivans were overpowering the PVE and GTA. You fought without support, without reinforcements, because all available assets were commited already. Things were stretched beyond the breaking point. As for the Shivans, they didn't need more than one or perhaps two capitals to wreak all the havoc they wanted. FreeSpace 1's missions are also designed to reflect a degree of desperation; a fight for absolute survival.

These things aren't true in FreeSpace 2 for the most part, and that fact made the game's sins as mentioned in the article much more grevious. It placed opposing sides on much more equal footings, where both sides had more than single capital ships available to commit and could have made good use of those extra ships. Also, though things certainly got desperate, they never deterioriated to the point they did in FS1; there was always a plan, and it was always feasible. These points also hold true for the vast majority of user-made campaigns and missions as well.

It is a prejudice. It is a prejudice against the recognition that letting the AI work for you can ''be'' good design (Clash of the Titans, the first one, called). It is a prejudice that conveniently forgets missions like Evangelist and the one that followed it, or Clash of the Titans, all the way back in FreeSpace 1. It is a prejudice against expanding the scope of your story so that it is clear Alpha 1 is not the sole savior of the universe and the Terran and Vasudan races, but part of a team; it could not have been done without him/her, but they could not have done it alone...or even that perhaps it could have been done without them, but at greater cost. It is a prejudice, in short, from telling a different story or telling the same story differently. And that in the end will be far more deadly to the community then bad design. To be blunt, Transcend's missions particularly as originally released were, from quite a few standpoints, not all that great in design. But Transcend is regarded as a must-play campaign, and it did truly transcend the boundaries of what most of us thought were the kind of stories that could be told through the medium of FreeSpace.

Someone saying you are "inexperienced" is hardly a slur, particularly as since compared to now, or even a year ago from this date, when that article was written FREDding was in its infancy. However because you seem to have taken personal offense, I did add a comment to this effect...though I would point out taking personal offense at that is frankly a sign that you shouldn't be editing this stuff because it is supposed to be unemotional. And as a statement of fact, as I already said, it's almost undoubtedly true.

Reverted.- [[User:Ngtm1r|Ngtm1r]] 01:44, 14 June 2008 (PST)

Battle of Endor syndrome has always referred to the tendency (mainly amongst novice FREDders) to make missions so large that they either crash the machine they are on or (usually due to the inexperience of the FREDder) are boring/unplayable. It does not refer to any mission which has a lot of ships in it. That is a big misuse of the term. Zarathud made it pretty clear in his original article what he was referring to. If you actually look at the missions that were being released at that time you'll see that the quality of the BoE missions was very low. The article served it's purpose of warning people of the dangers of trying to recreate Star Wars by simply sticking a few ships and events into a mission and hoping for the best.

Secondly, claiming that Zarathud was "inexperienced" is basically the same as saying STFU N00b rather than actually addressing his argument. That sort of thing has no place in a discussion (It's an ad hominem) let alone set in stone in a wiki article. Furthermore it's foolish to claim that the article was written that way simply because Zarathud was inexperienced because if I were to write an article on the subject I doubt it would be very different. I assume no one is dumb enough to try to claim I'm an inexperienced FREDder. :p

Furthermore FS2_Open has made it harder to make a good BoE mission in many ways. You can't get away with blaming flaws in your mission on things the engine won't let you do half as often because the engine allows you to do more. The bar is higher these days. So bad newbie missions that suffer from BoE look even worse.

BoE Syndrome is not a prejudice. It's nothing more than "No AWOL debrief syndrome" or any other syndrome you could make up from a common newbie mistake. - Karajorma 18/06/08

I think that the article is pretty balanced as it is. It warns of the difficulties of making these missions yet doesn't reject the BoE concept entirely, as the original version did.

The point is that Zarathud warned people ''not to make a BoE under any circumstances'', inexperienced or not. That's why this article has been changed from its original form. As for the personal drama, all of the ad homimem seems to be going on in this talk page, not the article. So I don't see a need for any changes to the article, if that's what either of you are suggesting. [[User:Mustang19|Mustang19]] 14:56, 20 June 2008 (CDT)

Yes he did warn them not to make BoE missions. However he also defined exactly what a Battle of Endor mission was. The missions you've picked as examples of good BoE missions have little resemblance to the one he gave. Instead of realising what the article is actually on about you've chosen to ignore that definition, assign your own strawman definition and then label him a n00b for believing it. As for ad hominem you haven't refuted Zarathud's article, you've simply said "Don't listen to him, he didn't know better when he said it." That is by definition an ad hominem since even if he was inexperienced that doesn't make a jot of difference as to whether he is right or not.

And he is right. As I said earlier I pretty much agree with every single thing he said in that article now (for retail) and most of it still applies to SCP. So either remove the flame on an active HLP member and argue on merit or I'll write my own article and dare you to say that I'm saying it cause I'm inexperienced as a FREDder. :p [[User:Karajorma|Karajorma]]

Talk:Battle of Endor Syndrome

2008-06-18T23:18:36Z

Karajorma:

Command-Line Reference

2007-09-02T10:02:54Z

Karajorma: /* Multiplayer */

==Launcher Flags==
The following command-line options can be chosen from the launcher.
===Graphics===
====-spec====
Enables specular mapping. Only polygons mapped with textures for which a shinemap exists will recieve specular mapping; no attempt is made to generate spec maps where they do not exist. Specular maps are specified with the base map name plus "-shine" (i.e. TCov3A-shine.pcx).
====-env====
Enables environment mapping. Environment mapping intensity will be determined from the intensity of specular maps. At the time of this writing (build 3.6.9 RC7), environment mapping only works when the video mode is OpenGL. [[Installing_fs2_open#Video setup|See Video setup.]]

====-glow====
Enables glowmapping. Only polygons mapped with textures for which a glowmap exists will be glowmapped. Glow maps are specified with the base map name plus "-glow" (i.e. TCov4A-glow.pcx)

====-jpgtga====
Enables the use of TGA and JPG file formats for image files. If a ship is showing up partially invisible, select this option.
Made default after 3.6.9

====-pcx32====
{{Warning|This will not improve the rendering of any ships in-game, and is usually more of a burden on performance than is worthwhile. Use at your own risk. Removed from launcher options post version 3.6.7.}}
Enables PCX files to be loaded into 32-bit memory.

====-cell====
Enables cell shading. This will make graphics appear more "cartoonish". For use with media in mv_cell.vp. Not considered a standard enhancement.
====-mipmap====
Enables mipmapping.

====-nomotiondebris====
Disables motion debris.
====-2d_poof====
Applies nebula poofs in 2d, effectively preventing them from forming intersections with ships.
====-noscalevid====
Disables scaling of video clips.
====-missile_lighting====
Applys lighting to missiles.
====-rlm====
{{Note| This option is not present in builds after [http://tinyurl.com/2yndle 2005/09/30] and is now always on.}}
Enables more accurate lighting model for OpenGL mode.

----

===Game Speed===
====-img2dds====
Converts all images to DDS (compressed) format. Decreases memory usage but potentially reduces image quality.
====-no_vsync====
Disables vertical sync.
====-cache_bitmaps====
Caches bitmaps between missions, which will ideally reduce the load-time from one mission to another.

----

===HUD===
====-dualscanlines====
Adds a second pair of scanning lines to the target window when scanning an object.
====-targetinfo====
Displays target info, such as name and class, beside the targeted object.
====-orbradar====
Enables 3D radar (the Orb). 3D radar will replace the standard 2D version.
====-ballistic_gauge====
Adds an ammo gauge to the HUD when armed with a ballistic weapon.
====-rearm_timer====
Displays time remaining until rearm and repair from a support ship is complete.

----

===Gameplay===
====-smart_shields====
Enables "smart" shield recharging. Shield recharge is distributed to the most damaged shield quadrant instead of being distributed equally across the entire shield and be wasted when a quadrant is full.
====-ship_choice_3d====
Use ship and weapon models in ship selection and weapon loadout. Completely disables the standard ANI interface on those screens.
====-3dwarp====
Use full geometry for the subspace warp effect.
====-warp_flash====
Enable a flash at warp in and warp out.
====-UseNewAI====
Tells the game to use new AI routines. This argument alters mission balance and is not considered a standard feature.
====-tbp====
Enable feature set for The Babylon Project
====-wcsaga====
Enable feature set for The Wing Commander Saga.

It does the following changes to the normal FS2 engine behaviour:
* It removes -class name in the briefing ship render window, (the window that appears when ship icons are clicked).
* It removes enemy names ingame for wings of ships.
* Enemies can scream when dying. (Without the flag only friendlies scream).

----

===Audio===
====-snd_preload====
Preload mission sounds. Useful in preventing game stuttering when sounds are played for the first time.
====-nosound====
Disables all sounds.
====-nomusic====
Disables music only.

----

===Multiplayer===
====-standalone====
Creates a standalone server.
====-startgame====
Once you launch and choose a pilot within the game, you will immediately have begun to host a game. This can be used in conjunction with several options to customize the game you create: -closed, -restricted, -password, -gamename, -allowabove, and -allowbelow. -startgame has no effect when -standalone is used.

See related: [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-restricted|-restricted]] [[Command-Line_Reference#-password|-password]] [[Command-Line_Reference#-gamename|-gamename]] [[Command-Line_Reference#-allowabove|-allowabove]] [[Command-Line_Reference#-allowbelow|-allowbelow]]

====-closed====
Hosts a new game in a closed state, where no one can join until the in-game "Close" button is cleared. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -restricted or -password.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-restricted|-restricted]] [[Command-Line_Reference#-password|-password]]

====-restricted====
Hosts a new game in a restricted state. The host is presented with option to accept or deny each client's request to join the game. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -closed or -password.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-password|-password]]

====-multilog====
Creates a log file with a summary of packets sent and received in multiplayer games. The file is saved as \data\multi.log within the active mod folder - or with main data folder if no mod is active.

====-clientdamage====
This feature is not available in current builds.

====-mpnoreturn====
Disables return to the flight deck screen after a mission completes.

----

===Troubleshooting===
====-fixbugs====
{{Note| This option is not present in builds post version 3.6.7 ([http://tinyurl.com/3eynan 2007/03/22]).}}
Originally used to disable certain crashing behavior as a stop-gap measure.

====-nocrash====
{{Note| This option is not present in builds post version 3.6.7 ([http://tinyurl.com/3eynan 2007/03/22]).}}
Originally used to disable certain crashing behavior as a stop-gap measure.

====-oldfire====
This feature is not available in current builds.

====-nohtl====
{{Warning| Enabling this will significantly reduce performance.}}
Reverts to software rendering mode.

====-no_set_gamma====
Disables the gamma settings in the options screen.
====-nomovies====
Disables all video playback.
====-noparseerrors====
Disables some parsing warnings and makes other parse errors non-fatal. Do not rely on this when creating new tables, the errors are there for a reason.
====-safeloading====
Loads missions the old way. Typically safer, but slower.
====-query_speech====
Determines if the current build includes text-to-speech.
====-d3d_bad_tsys====
Enable inefficient texture system.
====-novbo====
Disables OpenGL VBO.
====-noibx====
Disables IBX caching of model geometry data. This will dramatically increase load times, but will help troubleshoot a model if one is working incorrectly.
====-loadallweps====
Load all weapons, even those not used.

----

===Experimental===
====-alpha_env====
Enables alpha environment mapping. OpenGL only. Environment mapping intensity will be determined from the alpha channel of specular maps.
====-decals====
Enables damage decals.
(Decals have been disabled in builds after May 4, 2006)

====-ingame_join====
Enables ingame joining in multiplayer. FIXME: Host option?
====-tga16====
{{Note| This option is not present in builds post version 3.6.7 ([http://tinyurl.com/yr8tub 2006/04/05]).}}
Originally used to converts TGA images to 16-bits in order to reduce memory footprint (at the expense of image quality), superseded by [[Command-Line_Reference#-closed|-img2dds]].
----

===Development Tools===
====-fps====
Displays current frames per second.
====-pos====
Displays current position coordinates of camera.
====-window====
Runs the game in a window. No check to make sure that resolution is no higher than your desktop resolution, so be careful.
====-timerbar====
Displays a timing bar across the top of the screen. Timebar format varies by build.
====-stats====
Shows total and free physical memory, virtual memory and system pagefile.

====-coords====
Shows coordinates of the mouse cursor.
====-show_mem_usage====
Shows detailed RAM usage in HUD.

The meaning of the info displayed in the upper right corner is:

'''DYN''' = dynamic memory, basically anything that's been allocated by the vm_* memory functions. This does NOT indicate total memory usage but does account for most of it.

'''POF''' = model memory, how much memory is being used by models (does not include textures)

'''C-BMP, BMP''' = bmpman memory, how much is used by the textures/images that are loaded. C-BMP means that you are using -cache_bitmaps and it will try to keep textures in memory between level loads and as the new level is loading it will keep what it needs and unload what it doesn't. Can greatly increase level loading speed, but does so at the cost of memory between level loads. This does not increase overall memory usage though, only during the loading screen. BMP means that it is not cached and all textures are unloaded from memory at the start of level load and all needed textures are then loaded from the disk again.

'''S-RAM''' = sound memory, how much is used by the sounds loaded in memory at the time. This counts static sounds only (from sounds.tbl, etc.) and not streaming sounds (music, voices, briefing stuff, etc).

'''V-RAM''' = approximate memory usage of video textures. This does not mean that your card has this much memory, and can report higher numbers that your card actually has memory. For OpenGL it also includes some of the geometry data, but this number does not reflect the total memory that your video card is using. It only reports how much data the game has purposefully loaded into API memory (meaning it could be in system memory, video card memory, or AGP memory).

''(It only works with debug builds, not with release builds).''

====-pofspew====
Reads all objects in the pof file of the selected mod, and creates an ibx cache file for each object in the data/cache folder for that mod.
Details for each object are output to a pofspew.txt file created in the data folder.
Otherwise ibx files are created in game before each mission.

====-tablecrcs====
{{Sectstub}}

====-missioncrcs====
{{Sectstub}}

====-dis_collisions====
Disables all collisions.
====-dis_weapons====
Disables weapons rendering.
====-output_sexps====
Outputs SEXPs to sexps.html.
====-output_scripting====
Outputs scripting to scripting.html.
====-nograb====
Unix only. Disables focus grabbing in a window.
==Other==
The following options are not available as checkboxes in the launcher. Many require parameters, which follow the flag seperated by a space. The prototype for use in this case is "-option argument"
===Graphics===
====-ambient_factor====

This must be entered into the "Custom flags" field. This is a multiplier applied to the intensity of ambient lighting. Ambient light is lighting applied to all parts of a ship. FS2's standard value is 120. Try 75 for a good and realistic looking value. However, that is relative.

====-no_emissive_light====
By default, all ships in FS2 have a light generated on their own, it is more or less similar to a minimal amount of -ambient_factor. This feature was implemented to help the player seeing the ships over a black background. This flag disables this feature. Use it with a low -ambient_factor value to obtain an ultra realistic dark looking.

====-spec_exp====

This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts the size of the shiny spot on ships. Higher number mean smaller spots. Default is 16, however 11 is recommended. However, that is relative.

====-spec_point====

This must be used with the -spec command line parameter and must be entered into the
"Custom flags" field. Adjusts how much laser weapons contribute to specular highlights. Higher number mean greater contributions. Default is 1.0, however 0.6 is recommended. However, that is relative.

====-spec_static====

This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts how much suns contribute to specular highlights. Higher numbers mean a greater contribution. Default is 1.0, however is 0.8 recommended. However, that is relative.

====-spec_tube====

This must be used with the -spec command line parameter and must be entered into the "Custom flags" field. Adjusts how much Beam Weapons contribute to specular highlights. Higher numbers mean a greater contribution. Default is 1.0, however 0.4 is recommended. However, that is relative.

====-clipdist====
Changes the distance from the viewpoint for the near-clipping plane.

Takes one argument decimal specifying the distance to the near-clipping plane.

====-no_emissive_light====
'''''OpenGL Only'''''. Disables global emissive light. Shadows are darker. Objects are harder to see.

====-ogl_spec====
'''''OpenGL Only'''''. Takes a numerical argument. This value changes the basic shininess of the specular light in OpenGL. A lower value reduces the overall intensity of the light making it broader and less powerful. A higher value makes it more focued and brighter. The default value is 80, and the usable range is 0 to 128 (clamped). The original default value was 60, but it was raised to behave more D3D like.

----

===Gameplay===
====-mod====

Specifies in which folders inside Freespace2 directory, the game looks for all the game data (models, missions, textures, tables, ...). Retail version only looks inside ''Freespace2/data/'' structure and ''Freespace2/vp archives''.

This flag allows installing several different mods that modify retail behaviour, and switching between them without needing to erase files or having undesired cross effects. Each mod should be installed in its own folder.

It takes one argument string: the chain of names of the used directories. Comma (''',''') must be used as separator. In this way, '''-mod dir1,dir2,dir3,...,dirx''' causes the game to use the following directory precedence:

#Freespace2/dir1/
#Freespace2/dir2/
#Freespace2/dir3/
# ... (the rest of the typed directories) ...
#Freespace2/dirx/
#Freespace2/

:::Please note. Freespace Open doesn't like spaces in directories (in the full path) so do not install the game within ''Program Files/Freespace2'' or ''Games/Freespace 2'' and, of course, do not use spaces within mod directories (''dir1'' is OK but ''dir 1'' isn't).

This flag can be indirectly set, (and it is normally set), through Launcher MOD tab and mod.ini file. Within this Launcher tab you can select one directory, (let's call it ''moddir''), so the flag is at least set to '''-mod moddir'''. If ''Freespace2/moddir/mod.ini'' exists, (its format must be plain text), it will be read and, inside it, the following section and lines can be used to modify the -mod flag too:

[multimod]
PrimaryList = Pri1,Pri2,...(the rest of desired directories)...,Prix;
SecondaryList = Sec1,Sec2,...(the rest of desired directories)...,Secx;

(Please note the ending semicolon (;) in each list line). With these lines the following flag would be built:
: '''-mod Pri1,Pri2,...,Prix,moddir,Sec1,Sec2,...,Secx'''

If primary or secondary folders aren't used, their respective line can be erased or it can be typed as ''xxxxxxList = ;''.

::: '''''PLEASE NOTE''': '''Launcher v 5.4''', or later, '''must be used'''. Earlier versions had some bugs that would cause the previous explanation about mod.ini fail.''

::: The most common use of mod.ini and SecondaryList is sharing resources between mods. And the best example is the enhaced media vps from SCP crew. Most of the people install them in a folder called ''mediavps'' inside ''Freespace2''. In this way when running retail FS2 they do not interfere with this original game version that doesn't use this -mod flag feature. When using FS2_Open but without mods, you just need to select ''mediavps'' in Launcher MOD tab to use them. And if you want to enjoy that enhacements while playing any 'real' mod, you just need to put a mod.ini file inside its ''moddir'' with at least a ''SecondaryList = mediavps;'' line.

Nested directories can be also used. As example imagine that you have all your mods inside a main folder called ''MyMods'' and that shared resources like Media VPs are also in another folder called ''Resources''. In this way you could have:

*/Freespace2/MyMods/ModWhatever1/
*/Freespace2/MyMods/ModWhatever2/
*...
*/Freespace2/MyMods/ModWhateverx/
*/Freespace2/Resources/mediavps/

Then imagine that you want to use ''ModWhatever1'' with ''mediavps'' enhacement. Your mod flag should be set to '''-mod MyMods/ModWhatever1,Resources/mediavps'''. Like always, you could type this flag as a custom flag or you could select ''MyMods/ModWhatever1'' in Launcher MOD Tab and in its mod.ini file type:

[multimod]
SecondaryList = Resources/mediavps;

Please note that your path structure will use \ instead of / in a Windows environment.

'''Data precedence'''

Inside each directory, data precedence is the following:

#Individual files located in ''Current_dir/data/'' subdir structure. See [[FS2_Data_Structure|FS2 Data Structure topic]] for deeper info about the different folders and contents this structure has.
#Files located inside vp archives. (These vp archives are 'similar' to zip archives, they just contain other files and folders. Moreover, files have to be stored using the same ''data/'' structure used outside it). Vp archives are read in alphabetical order so aaa.vp files have higher priority than aab.vp files and so on.

The highest priority file overrides the rest of them. In this way, if you have a ''Mission.fs2'' inside ''Freespace2/Pri1/data/missions/'' it doesn't matter how this ''Mission.fs2'' is inside ''Freespace2/Pri1/aaa.vp'', ''Freespace2/Pri1/aab.vp'', ... or ''Freespace2/data/missions/''. This data precedence allows the user to quickly replace old files by corrected or enhaced ones adding them in a higher priority place.

'''Additional notes'''

# In systems running Windows use '''\''' instead of '''/''' as directory separator.
# As derived from the explanation, the exact names for directories or vp archives are actually irrelevant. It only matters the directory order inside -mod flag argument and the alphabetical order for vp archives inside each used directory.
# This flag is also used by FRED. So if there is special mod info, (like backgrounds maps, ship models or whatever), it must be typed, (''Fred2_Open_r.exe -MOD whatever''), or FRED won't be able to use it. No Launcher MOD tab is available for this use.
# Be careful while typing the directory names in the flag argument or inside mod.ini files. The program doesn't check if the typed directories exist. If they do not exist, they are just ignored. No warnings, no errors, no messages at all.

:'''VERY IMPORTANT INFO ABOUT PRIORITY AND TEXTURE FORMATS'''

:FS2_Open can use several file formats in textures: PCX, DDS, JPG and TGA (the last two need the flag [[Command-Line_Reference#-jpgtga|-jpgtga]]). '''Always update every texture keeping its format'''. For example if you update the old ''TextureOfMyFighter.tga'', do not save it as ''TextureOfMyFighter.dds'' in a higher priority place, because there is a chance of the game loading the old one despite of all.

:The reason to do this is that, at least in FS2_Open v3.6.9. and previous versions, loading process (including priorities) is applied firstly for a kind of textures (TGAs), then for another kind (JPGs), and so on. The exact order of this global texture type priority may change in the future but nevertheless there is always going to be a fixed loading order between them. This behaviour can lead to situation where your new, updated and higher priority placed texture is not read because the format of the older one. (An example of this situation can be found in [http://scp.indiegames.us/mantis/view.php?id=1123 this false Mantised Bug 1123]).

:The reason of this behaviour relays in the way the game looks for files. Without this way of coding, the number of file searches would hugely increase, so mission loading times would be much higher.

====-fov====
Specifies the Field of View for the player eyepoint.

Takes one argument decimal specifying the angle of the viewing cone in radians, from 0 to 2*pi

You can set the cone of view making things look bigger/smaller. The problem with this is that if you choose a small FOV, you will have a squashed look on the edges of your screen - stretched edges with a too high FOV. It is recommended to change the FOV as FS2 normally has some perspective distortion at the screen edges (FOV too high). Set the FOV to something like 0.39 - it will fix the distortion problem, and (as a nice side effect) will make everything look bigger and more realistic scale-wise. The default is 0.75, if you go higher, you'll get the fish-eye effect. Feel free to experiment. This must be entered into the "Custom flags" field

''Because of an active bug, FOV can misalign target boxes, effects, etc. Please check [http://lore.maxgaming.net/~scp/mantis/bug_view_advanced_page.php?bug_id=0000083 Mantis bug 083 status]if you are going to change the default value. Even with the default value, (no flag), there are small distortions.''

----

===Multiplayer===
====-gamename====
Specifies the name of the game to be created by the host. This only works when used in conjunction with -startgame.

Takes one argument string, the name to be assigned to the game being created.

This argument does nothing when used with -standalone. To set the name for a standalone server, see [[Multiplayer(Main)#Standalone Servers|Standalone Servers]].

See related:   [[Command-Line_Reference#-startgame|-startgame]]   [[Multiplayer(Main)#Standalone Servers|Standalone Servers]]

====-password====
Specifies the password for a stand-alone server. This only works when used in conjunction with -startgame. Cannot be used in conjunction with -closed or -restricted.

Takes one argument string, the required password for the game being created.

See related: [[Command-Line_Reference#-startgame|-startgame]] [[Command-Line_Reference#-closed|-closed]] [[Command-Line_Reference#-restricted|-restricted]]

====-allowabove====
Specifies a player's minimum rank for joining a game. This only works when used in conjunction with -startgame.

Takes one argument integer, the points ranking above which a player must be to enter the game.

See related: [[Command-Line_Reference#-startgame|-startgame]]

====-allowbelow====
Specifies a player's maximum rank for joining a game on a stand-alone server. This only works when used in conjunction with -startgame.

Takes one argument integer, the points ranking below which a player must be to enter the game.

See related: [[Command-Line_Reference#-startgame|-startgame]]

====-port====
Specifies the port on which to host a game or serve a stand-alone game.

Takes one argument integer, the port on which the host will listen for clients.

====-connect====
{{Sectstub}}

====-timeout====
{{Sectstub}}

====-cap_object_update====
Caps the maximum object update the server will respond to regardless of what the client has set. If the client is set to request high object updates but the server is capped to low then that's all the client will get.

Takes one argument integer (0 to 3) which corresponds to the object update cap (With 0 being low and 3 being LAN).

[[Category:Lists]]
[[Category:Source Code Project]]

Ai.tbl

2007-01-13T08:47:25Z

Karajorma: /* Patience */

*The AI.tbl file defines the AI classed used in the game. This table is used to define each AI class with four abilities for each of the five difficulty levels.

==Ability==
*Higher number means better ability

===Accuracy===
*How accurately ship uses its weapons

===Evasion===
*How good the ship is at evading

===Courage===
*How likely the ship is to chance danger to accomplish goals

===Patience===
*How willing the ship is to wait for an advantage before pursuing goals (Never actually implemented - It does nothing)

==Table Entry==
'''$Name:'''
*Defines a name for the AI class that can be used with ships.tbl and also with FRED
*Syntax: ''Name''
'''$accuracy:'''
*Value from 0.0 to 1.0
*Syntax: ''Value, Value, Value, Value, Value''
**Very Easy, Easy, Moderate, Hard, Very Hard difficulty levels respectively
'''$evasion:''', '''$courage:''' and '''$patience:'''
*Value from 0 to 100
*Syntax: ''Value, Value, Value, Value, Value''
**Very Easy, Easy, Moderate, Hard, Very Hard difficulty levels respectively

==Sample Entry==
#AI Classes
$Name: Captain
$accuracy: 0.5 0.55 0.6 0.65 0.7
$evasion: 10, 20, 30, 40, 50
$courage: 10, 20, 30, 40, 50
$patience: 10, 20, 30, 40, 50
#End

[[Category:Tables]]

Ai.tbl

2007-01-13T08:46:29Z

Karajorma: /* Patience */

*The AI.tbl file defines the AI classed used in the game. This table is used to define each AI class with four abilities for each of the five difficulty levels.

==Ability==
*Higher number means better ability

===Accuracy===
*How accurately ship uses its weapons

===Evasion===
*How good the ship is at evading

===Courage===
*How likely the ship is to chance danger to accomplish goals

===Patience===
*How willing the ship is to wait for an advantage before pursuing goals (Never actually implimented - It does nothing)

==Table Entry==
'''$Name:'''
*Defines a name for the AI class that can be used with ships.tbl and also with FRED
*Syntax: ''Name''
'''$accuracy:'''
*Value from 0.0 to 1.0
*Syntax: ''Value, Value, Value, Value, Value''
**Very Easy, Easy, Moderate, Hard, Very Hard difficulty levels respectively
'''$evasion:''', '''$courage:''' and '''$patience:'''
*Value from 0 to 100
*Syntax: ''Value, Value, Value, Value, Value''
**Very Easy, Easy, Moderate, Hard, Very Hard difficulty levels respectively

==Sample Entry==
#AI Classes
$Name: Captain
$accuracy: 0.5 0.55 0.6 0.65 0.7
$evasion: 10, 20, 30, 40, 50
$courage: 10, 20, 30, 40, 50
$patience: 10, 20, 30, 40, 50
#End

[[Category:Tables]]

Template:Recent FRED Additions

2006-06-02T10:54:23Z

Karajorma:

{| border=0 align=center cellpadding=4 cellspacing=0 width=70% style="margin: 0 0 1em 1em; background: #404040; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #613030; 70%; font-size: 125%;" width="100px" |
! style="color: white; height: 30px; background: #613030; 70%; font-size: 125%;"|'''Most Recent FRED Additions'''
! style="color: white; height: 30px; background: #613030; 70%; font-size: 75%;" align="right" width="100px" | [http://www.hard-light.net/wiki/index.php?title=Template:Recent_FRED_Additions&action=edit Edit]
|-
| style="background:#100505;" colspan="3"|
''SEXPs:''

* [[disable-builtin-messages]]
* [[enable-builtin-messages]]
* [[num-assists]]
*[[lock-primary-weapon]]
*[[unlock-primary-weapon]]
*[[lock-secondary-weapon]]
*[[unlock-secondary-weapon]]
----
''Features:''

* [[Improved Team Loadout]]
|-
|}

Improved Team Loadout

2006-06-02T10:50:05Z

Karajorma: /* Setting Up The Next Mission */

Team Loadout has been improved to allow the use of variables as well as numbers to determine how many ships will be available. The heart of the new system is the updated Team Loadout panel of course.

http://www.hard-light.net/images/wiki/TeamLoadoutEditor.jpg

The most important addition is the Set Amount from Variable. The list presented to the player shows all the available number SEXP variables. In the example shown the NumberOfHercIIs variable has been set to 5 but since this is a [[Persistent Variables|persistent variable]] any previous mission could set this to another number.

The From Variable list gives you access to another powerful feature. Not only can the number of ships available be set from a variable. The class of the ship itself can also be set from a string variable. That means you can determine the loadout of one mission in the one preceeding it.

The Team Loadout Editor only affects the number of ships that will be available in game but it won't touch the ships that have been specified in the mission file by default. If you set up Alpha wing to consist of 4 GTF Ares that's what you will get by default. If however you go to the Ship Editor and select the Set Class Dynamically the ship class will be set based on what is left in the Loadout.

http://www.hard-light.net/images/wiki/SetClassDynamically.jpg

For every ship that has the Set Class Dynamically box ticked the game does the following : -

# Check if the ship specified in the mission file was set to be available in the loadout and if there are any left. If so the number left is decreased by one.
# Check if the ship fits one one of the Alt Ship Classes (more on these later). If so the ship is changed to that class.
# Loop through the loadout in the order they appear in Ship.tbl and set it to first class that it can find any ships available for.
# If all the above has been unsuccessful the game sticks with what was supplied in the mission file.

Note that the game does this for '''every''' ship that has been told to Set Class Dynamically not just Alpha, Beta and Gamma wings. It is quite possible to use this feature to set the class of any ship in the mission (Although using it with anything other than ship classes that the player can fly is pointless)

http://www.hard-light.net/images/wiki/AltShipClassEditor.jpg

The Alternate Ship Classes Editor gives the mission designer a way to fine tune which ships will be selected by the game. Alt Class Type 1 acts as a suggestion. The game will try to set the ship class to that if there are any ships of that class remaining. Alt Class Type 2 however is more of an order. If one of these is given that will be the ship class that the ship ends up with if it couldn't find a match earlier on. Note that Alt Classes are completely optional.

Here's a run down of what will happen for the ship that the Alt Ship Class Editor pictured above belongs to.

# Check the class in the mission file has any remaining ships.
# Check the first type one alt class (if any). In this case it's a Herc Mark II.
# Check 2nd and 3rd type one alt classes. In this case that's an Erinyes and whatever the AltClass01 String Variable holds
# If the above steps have failed the game then notices that the GTF Hercules has been specified as the Type 2 Alt Classs. The ship will be a Herc. Had no Type 2 been specified the game would then start looping through the entire loadout as described above.

==Setting Up The Next Mission==

When it comes to setting up the team loadout variables you have several options. You can roll your own events to set up everything but this could get tedious. Work on constructing SEXPs to alter the the loadout depending on ships which departed or were destroyed are on their way. Till then the deal-with-ship-loadout will automatically sort out the loadout variables for any destroyed ship that had set the Team Loadout Store Status box clicked for it. Don't release anything using this SEXP though since it is subject to change or removal.
[[Category:FRED]]

Template:Recent FRED Additions

2006-06-02T10:49:00Z

Karajorma:

{| border=0 align=center cellpadding=4 cellspacing=0 width=70% style="margin: 0 0 1em 1em; background: #404040; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #613030; 70%; font-size: 125%;" width="100px" |
! style="color: white; height: 30px; background: #613030; 70%; font-size: 125%;"|'''Most Recent FRED Additions'''
! style="color: white; height: 30px; background: #613030; 70%; font-size: 75%;" align="right" width="100px" | [http://www.hard-light.net/wiki/index.php?title=Template:Recent_FRED_Additions&action=edit Edit]
|-
| style="background:#100505;" colspan="3"|
''SEXPs:''

* [[disable-builtin-messages]]
* [[enable-builtin-messages]]
* [[num-assists]]
----
''Features:''

* [[Improved Team Loadout]]
|-
|}

Portal:FRED

2006-06-02T10:42:53Z

Karajorma:

{| border=0 align=center cellpadding=4 cellspacing=0 width=95% style="margin: 0 0 1em 1em; background: #404040; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #613030; 70%;"|'''The FRED Portal'''
|}

{| border=0 align=right cellpadding=4 cellspacing=1 width=200 style="margin: 0 0 1em 1em; background: #404040; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #613030; 70%;"|'''''Learning FRED'''''
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[5 Easy steps towards your FREDucation|5 Easy Steps]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[:Category:FRED Tips|FRED Hints and Tips]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[:Category:FRED Mistakes|Common FRED Mistakes]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[:Category:FRED Examples|FRED Examples]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|'''''SEXPs'''''
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Retail SEXP Reference|Retail SEXPs]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[SCP SEXP Reference|SCP SEXPs]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|'''''New FRED Features'''''
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Skybox|Skybox]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Texture Replacement|Texture Replacement]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[FRED Command Line Reference|Command Line Options]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Persistent Variables|Persistent Variables]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Improved Team Loadout|Improved Team Loadout]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Minor FRED Features|List of Minor Features]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|'''''Mission Designer's Reference'''''
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Nebula background|Nebula Backgrounds]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Friendly wing names|Friendly Wing Names]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Enemy wing names|Enemy Wing Names]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Freespace 2 Ship Database|FS2 Ship Database]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Stars and Planets|Stars and Planets]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|'''''FRED Troubleshooting'''''
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Known FRED Problems|Known Problems]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Common FRED Issues|Common Issues FAQ]]
|-
|}
Welcome to the FRED portal. Here you will find tips, guides, reference material and other information regarding the Freespace Editor as well as mission design in general. This page is not yet completed, but feel free to help fill in any articles and categories you think are missing.
 
{{Recent FRED Additions}}
==See Also==
*[[The FRED Academy]]

==Related Links==
*[[Portal:Modding|The Freespace Modding Portal]]
*[[User-made Campaigns]]

==External Links==
*[http://www.woodentoyandgift.com/GTD/fred/ Online FRED Walkthrough]
*[http://www.hard-light.net/forums/index.php/topic,34852.0.html Download latest FRED builds]
[[Category:Modding]]
[[Category:FRED]]

Improved Team Loadout

2006-05-29T21:24:39Z

Karajorma:

Portal:FRED

2006-04-29T14:43:39Z

Karajorma:

{| border=0 align=center cellpadding=4 cellspacing=0 width=95% style="margin: 0 0 1em 1em; background: #404040; border: 1px
#CC0500 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #613030; 70%;"|'''The FRED Portal'''
|}

{| border=0 align=right cellpadding=4 cellspacing=1 width=200 style="margin: 0 0 1em 1em; background: #404040; border: 1px

#CC0500 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #613030; 70%;"|'''''Learning FRED'''''
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[5 Easy steps towards your FREDucation|5 Easy Steps]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[:Category:FRED Tips|FRED Hints and Tips]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[:Category:FRED Mistakes|Common FRED Mistakes]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[:Category:FRED Examples|FRED Examples]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|'''''SEXPs'''''
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Retail SEXP Reference|Retail SEXPs]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[SCP SEXP Reference|SCP SEXPs]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|'''''New FRED Features'''''
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Skybox|Skybox]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Texture Replacement|Texture Replacement]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[FRED Command Line Reference|Command Line Options]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Persistant Variables|Persistant Variables]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Improved Team Loadout|Improved Team Loadout]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Minor FRED Features|List of Minor Features]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|'''''Mission Designer's Reference'''''
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Nebula background|Nebula Backgrounds]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Friendly wing names|Friendly Wing Names]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Enemy wing names|Enemy Wing Names]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Freespace 2 Ship Database|FS2 Ship Database]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Stars and Planets|Stars and Planets]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|'''''FRED Troubleshooting'''''
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Known FRED Problems|Known Problems]]
|-
! style="color: white; height: 30px; background: #404040; 70%;"|[[Common FRED Issues|Common Issues FAQ]]
|-
|}
Welcome to the FRED portal. Here you will find tips, guides, reference material and other information regarding the Freespace Editor as well as mission design in general. This page is not yet completed, but feel free to help fill in any articles and categories you think are missing.
 
{{Recent FRED Additions}}
==See Also==
*[[The FRED Academy]]

==Related Links==
*[[Portal:Modding|The Freespace Modding Portal]]
*[[User-made Campaigns]]

==External Links==
*[http://www.woodentoyandgift.com/GTD/fred/ Online FRED Walkthrough]
*[http://www.hard-light.net/forums/index.php/topic,34852.0.html Download latest FRED builds]
[[Category:Modding]]
[[Category:FRED]]

Installing FreeSpace 2

2006-01-28T19:09:29Z

Karajorma: /* How do I install FS2? I have the I have the retail CDs */

==How do I install FS2? I have the I have the retail CDs==

The FS2 installer is pretty easy to use so I'm only going to point out a few pitfalls that could cause you problems later rather than guide you through the whole install.

<ul type="disc">
<li>Do not install to C:\Program Files - Don't use any path with a space or a hyphen in it. This may cause you minor problems when using FS2_Open later. C:\Games is fine for instance.</li>
<li>Do not untick the High Resolution Artwork - Unless you want to doom yourself to playing in 640x480 (Even in FS2_Open you may have problems with higher resolutions). </li>
<li>If you skip the other options, you may copy them from the CD later.</li>

</ul>

Congratulations you now have a (hopefully) working copy of FS2. Even if you intend to install FS2_Open next you should run the game once. First to check if there are any problems and second cause you'll have to start the game once before you can patch it to 1.2 (which you should do regardless of whether or not you'll be using FS2_Open). Playing long enough to see the tutorial start should be long enough to detect most problems. Since you can skip the training sims if you have to restart you may wish to play the first one through anyway. You can then quit and run the updater in the FS2 launcher.

Installing FreeSpace 2

2006-01-28T19:06:22Z

Karajorma:

==How do I install FS2? I have the I have the retail CDs==

The FS2 installer is pretty easy to use so I'm only going to point out a few pitfalls that could cause you problems later rather than guide you through the whole install.

<ul type="disc">
<li>Do not install to C:\Program Files - Don't use any path with a space or a hyphen in it. This may cause you minor problems when using FS2_Open later. C:\Games is fine for instance.</li>
<li>Do not untick the High Resolution Artwork - Unless you want to doom yourself to playing in 640x480 (Even in FS2_Open you may have problems with higher resolutions). </li>
<li>If you skip the other options, you may copy them from the CD later.</li>

</ul>

Congratulations you now have a (hopefully) working copy of FS2. Even if you intend to install FS2_Open next you should run the game once. First to check if there are any problems and second cause you'll have to start the game once before you can patch it to 1.2 (which you should do before trying to install FS2_Open). Playing long enough to see the tutorial start should be long enough to detect most problems. Since you can skip the training sims if you have to restart you may wish to play the first one through anyway. It will give you an appreciation of the advances in FS2_Open if you do see the original in action. You can then quit and run the updater in the FS2 launcher.

Installing fs2 open

2006-01-16T23:43:36Z

Karajorma: /* Official Releases */

This guide assumes you already have a working copy of Freespace 2 installed. If not, see [[Installing Freespace 2]]. Also, this build assumes you do not use an installer. If you do, skip down to the part where it talks about configuring fs2_open.

== Step One: Understanding what you need ==

There are three main components that you need to get the most out of fs2_open.

First, the Launcher. This lets you configure the fs2_open executable for your particular system, in much the same way the original Freespace 2 launcher is used to configure it.

Next, the fs2_open build. This is the core game engine, a single executable file.

Finally, the MediaVPs. These contain all sorts of graphical improvements and are highly recommended. Version numbers of mediaVPs generally agree with the fs2_open build that they're supposed to be used with.

== Step Two: Getting the Launcher ==

Unless you are using an extremely old build, you will want to get Launcher 5.3. Otherwise, go with Launcher 4. To install either, extract it to your main Freespace 2 folder. (You can have both on your computer at the same time, although it's not recommended)

[http://scp.indiegames.us/download.php?view.133 Launcher 5.3 download page]

== Step Three: Choosing a build ==
There are two main types of fs2_open builds, at the time of this writing. A "build" is any executable built from source code. Any build may also be a debug build. (Debug builds usually have names that end with "_d" or "_dbg" or somesuch) If you don't know why you'd want to use a debug build, you're almost certainly better off not using one.

All builds should be extracted to your main Freespace 2 folder.

=== Official Releases ===
The first type is the "stable" release build. Depending on the version, there may be some minor bugs that made it into the final release. (In 3.6, you can't warp out in Very Easy difficulty; in 3.6.5, OGG music, and thus the MediaVP package mv_music, will cause a crash to desktop, 3.6.7 has issues with dual core processors). However, they are more consistently stable than "recent builds", as they represent a group effort to get a stable build out, by all coders on the [[FSSCP]].

Additionally, some official release builds are available with installers. It's a good idea to get the most recent official release, even if you end up deciding to get a recent build anyway.

[http://scp.indiegames.us/download.php?list.8 Official release download page]

=== Recent Builds ===
Recent Builds are ones that individual coders release. These may be more stable than Official Releases, in some cases. Most of the time they're released to either test or showcase some particular new feature. If you're curious about how reliable a build is, your best bet is to check the original thread it was posted in and see what people's responses were.

[http://scp.indiegames.us/download.php?list.7 Recent builds download page]

== Step Four: Choosing your MediaVPs ==

There are a variety of different [[MediaVP]]s available for download. No matter what system you have, it should be able to support mv_core with no degradation in performance. This will enable a few interface improvements that require extra art.

mv_music should only be used with builds from April 2005 or after. mv_models should not be used on systems that do not support HT&L (video cards such as the TNT2 and below do not support HT&L). mv_adveffects should only be used if you have an extremely high-end system. (In the neighborhood of an X800 or 6800, and with a P4 or AMD64 processor.) The rest of the MediaVPs can be installed as your computer allows. (You may want to download them one at a time after you have configured fs2_open so you can get an idea of how much they will slow fs2_open down)

There are two ways to set up the media VPs. The quick and dirty method is to simply dump them in your main Freespace 2 folder. This will allow FS2_open to work but will prevent you from playing the standard retail version or from playing games on FS2NetD (The FS2 online service) without getting a "hacked tables" error message. The second way preserves both of these and requires minimal extra time to set up. (See step six for further details)

[http://scp.indiegames.us/download.php?list.2 MediaVP download page]

== Step Five: Configuring Everything ==

=== Basic setup ===

At this point, you have one final stage remaining before fs2_open is ready to go. Open up the Launcher. (It should be in your main Freespace 2 folder). Select the EXE you'd like to use by clicking the "Browse..." button at the top of the Launcher.

Next, ensure that the "Audio/Joystick" and "Network" tabs have the proper settings. (If you have trouble with your joystick not working properly in fs2_open, you may try the "Force 0" or "Force 1" options, which will force fs2_open to use the first or second joysticks, respectively.

=== Speech setup ===

If you are using Windows XP, or have the Speech API installed, fs2_open will be able to read briefings, techroom descriptions, and even ingame messages to you using computer-generated voices. Although no match for real voice acting, it is convenient when valid plot points are mentioned in the middle of combat. Speech in the various locations can be turned on and off by checking and unchecking the check boxes; you can choose which of the installed voices to use in fs2_open by changing the drop-down menu. As of this writing, fs2_open will only use the voice you choose for everything.

=== Video setup ===

On the "Video" tab, you can choose which API to use (OpenGL or Direct3D), what resolution to run in, and whether to use anti-aliasing (Multisampling) or not. Note that if you're using an ATI card, with Catalyst drivers above 4.3, shinemaps will not work in Direct3D. However, environment mapping will not work in OpenGL.

"Allow non standard modes" will let you choose resoltuions other than 1024x768 and 640x480. There may be some small graphics alignment errors, but these are generally small and virtually unnoticeable.

=== Features setup ===

This tab is where most of fs2_open's options can be toggled on and off. At the top is a readout of your current command line; you should include this in any debugging reports you make.

The next box, with the buttons "Select mod" and "No mod" allow you to choose a mod directory to use; files in the mod directory will be given precedence over other files, so you can easily switch between mods by installing them to different directories.

"Custom flags" allows you to add any command line flags that don't show up in the Launcher. This may be because they require additional arguments, as is the case with the "-fov" command line argument. For more information, see the [[Command Line Flags]] page.

Finally, the two boxes below this let you toggle the various new features in fs2_open, many of which are graphical improvements. Recommended options for midrange systems are "Enable specular", "Enable glowmaps", "Enable jpg,tga textures", "Enable more realistic lighting", and "Load only used weapons". (You may have to choose a different section in the drop-down box to get to some of these days). There are many, many more options, but these should get you started.

[http://www.hard-light.net/wiki/index.php/Command-Line_Reference Command line Flags]

== Step Six: (Optional) Preserving Freespace 2 ==

At this point, if you try to start the original Freespace 2 executables, they'll likely crash at some point or other. To prevent this, do the following:

=== Move the mediaVPs to a mod dir ===
You can take advantage of the SCP's -mod feature and move the mediaVPs to a folder inside your main Freespace 2 folder; this folder can be named anything you like, such as "scp" or "mediaVPs". However, whenever you run Freespace 2, you must remember to select that folder as the current mod. If you want to play another mod, you must make use of the SCP's multiple mod feature.

=== Save any existing pilot files ===
Fs2_open upgraded the pilot files to allow for better mod handling in version 3.6.5. To prevent double entries from showing up, a new, upgraded version of the pilot file is created, and then the old one is deleted. To save your progress, copy all *.plr, *.csg, and *.css files that start with your pilot name. Then, rename the copies so that they're in the form of <your name>_scp. For example, my player file would be called "WMCoolmon_scp.plr". Then, only use the "_scp" versions when running fs2_open.

It's recommended you back up the originals as well, in case you accidentally click on the non-SCP version while in the SCP. (It should warn you that it's going to destructively convert them, however.)

[[Category:Source Code Project]]