Difference between revisions of "Source Code Project"
m (Distance between parts reduced.) |
(→The SCP Staff) |
||
(14 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
− | + | '''Source Code Project''', or '''SCP''', refers to the open-source modification of the retail FreeSpace 2 engine called FreeSpace Open. | |
− | + | ==History== | |
− | + | Now recorded here: https://github.com/scp-fs2open/fs2open.github.com/wiki/History-and-Release-Timeline | |
− | + | ==The SCP Staff== | |
− | + | The FSSCP is headed up by [https://www.hard-light.net/forums/index.php?action=profile;u=7220 The_E]. Former heads include [https://www.hard-light.net/forums/index.php?action=profile;u=5478 chief1983], [https://www.hard-light.net/forums/index.php?action=profile;u=561 Goober5000], [https://www.hard-light.net/forums/index.php?action=profile;u=1252 Taylor] and [https://www.hard-light.net/forums/index.php?action=profile;u=122 Inquisitor]. | |
− | The | + | The project leaders keep the team organized and working towards set goals. They will request a 'code freeze' before a major release, when programmers aren't supposed to add new features, and instead focus on cleaning up existing bugs. When the team is not preparing for a release, individual programmers are given a lot of leeway in what they can work on. |
− | |||
− | + | Not only does the SCP team enhance the graphics and the gameplay of FreeSpace, modders can also add their own features into the mods they are working on. The FSSCP allows mod development teams, campaign builders, and individual mission makers to add features that will enhance their work. | |
− | |||
− | + | Established projects that need features and who are involved in the community will usually have their requested features added first, but if you have any great ideas, please post them in the [https://www.hard-light.net/forums/index.php/board,50.0.html FSSCP Forum] on the [https://www.hard-light.net/forums/ Hard-Light Productions Forums] (Be sure to do a search first so you're not reposting ideas). | |
− | + | While the developers are hard at work implementing new features, a critical area that you can help in is reporting bugs and helping coders to track them down. The place to do all of this bug tracking is [https://github.com/scp-fs2open/fs2open.github.com GitHub], the repository currently used by the FSSCP team. To learn more, please check out the article covering [[Bug Reporting]] | |
− | The | ||
− | + | == Release Timeline == | |
− | + | Now recorded here: https://github.com/scp-fs2open/fs2open.github.com/wiki/History-and-Release-Timeline | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Other Links == | == Other Links == | ||
Line 39: | Line 28: | ||
I know you worked on this article initially WMCoolmon, but I think as documentation it is "presenter" neutral? This info should go in another section as well. | I know you worked on this article initially WMCoolmon, but I think as documentation it is "presenter" neutral? This info should go in another section as well. | ||
− | Finally, | + | Finally, WMCoolmon occassionally releases new versions of the [[MediaVP]]s, which are a collection of better-quality textures and effects for FreeSpace 2. MediaVP development is separate from the SCP proper, but intimately related in that it shows off some of the features the team has implemented. |
--> | --> | ||
<!-- These sections should not be in this article commenting out until they are placed/edited | <!-- These sections should not be in this article commenting out until they are placed/edited | ||
− | == | + | ==Installation== |
There are three basic things you'll need or want to get FS2_Open running. | There are three basic things you'll need or want to get FS2_Open running. | ||
Line 54: | Line 43: | ||
− | == | + | ==Pitfalls== |
− | If you're using an old system, you may find that | + | If you're using an old system, you may find that FS2 Open runs slowly (or not at all). [http://dynamic4.gamespy.com/~freespace/forums/showthread.php?threadid=27037 tom's build] is the most bug-free version, though some features have been removed for the sake of stability. This build uses the old FreeSpace 2 graphics engine, but adds some of the new non-graphics improvements. Mostly, it'll let you play online using the new [[Fs2NetD]]. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | ===Multiplayer=== | ||
+ | Register at the [http://www.burbworld.com/fs2netd/register.php Fs2NetD site]. Then, in FreeSpace 2, enter your account username and password into the options screen (just like you would for PXO). Then, create a multiplayer pilot and try to start a multiplayer game. Keep in mind that if you don't have mv_core installed or a valid .cfg file, you won't be able to connect. Also, if you've got any mods installed (and aren't using the mod-switching feature) you'll be booted when you try to connect. | ||
− | == | + | ==Buf reporting== |
− | + | Before reporting, make sure it's a new bug. Go to the [http://dynamic4.gamespy.com/~freespace/forums/forumdisplay.php?forumid=50 FSSCP Forum] and type in some relevant phrase in the search box in the upper right of the page. For example, "Joystick not working". Look for any threads that seem like they might have something to do with the problem. | |
If you don't find any threads about the problem, check [http://mgo.maxgaming.net/mantis/main_page.php Mantis]. If you don't feel like registering, use the account: | If you don't find any threads about the problem, check [http://mgo.maxgaming.net/mantis/main_page.php Mantis]. If you don't feel like registering, use the account: | ||
<br><b>Username:</b> <tt>SCPGuest</tt> | <br><b>Username:</b> <tt>SCPGuest</tt> | ||
<br><b>Password:</b> <tt>password</tt> | <br><b>Password:</b> <tt>password</tt> | ||
− | |||
Finally, post a thread about it in the FSSCP forum or report it using Mantis. Of course, you could do this first, but you risk annoying people by re-asking about a bug that's been asked about before. | Finally, post a thread about it in the FSSCP forum or report it using Mantis. Of course, you could do this first, but you risk annoying people by re-asking about a bug that's been asked about before. | ||
− | An example of this is the warp-failure bug in 3.6. It turned out that in Very Easy difficulty mode, you would never be able to warp out of a mission. This bug was quickly corrected and a notice (along with a link to the corrected build) added to the top of the 3.6 release thread, but threads continually cropped up about it (sometimes more than one a day. | + | An example of this is the warp-failure bug in 3.6. It turned out that in Very Easy difficulty mode, you would never be able to warp out of a mission. This bug was quickly corrected and a notice (along with a link to the corrected build) added to the top of the 3.6 release thread, but threads continually cropped up about it (sometimes more than one a day). People got tired of replying to threads asking about it. |
--> | --> | ||
− | [[Category:Source Code Project]] | + | [[Category:Source Code Project|*]] |
Latest revision as of 21:15, 2 September 2018
Source Code Project, or SCP, refers to the open-source modification of the retail FreeSpace 2 engine called FreeSpace Open.
History
Now recorded here: https://github.com/scp-fs2open/fs2open.github.com/wiki/History-and-Release-Timeline
The SCP Staff
The FSSCP is headed up by The_E. Former heads include chief1983, Goober5000, Taylor and Inquisitor.
The project leaders keep the team organized and working towards set goals. They will request a 'code freeze' before a major release, when programmers aren't supposed to add new features, and instead focus on cleaning up existing bugs. When the team is not preparing for a release, individual programmers are given a lot of leeway in what they can work on.
Not only does the SCP team enhance the graphics and the gameplay of FreeSpace, modders can also add their own features into the mods they are working on. The FSSCP allows mod development teams, campaign builders, and individual mission makers to add features that will enhance their work.
Established projects that need features and who are involved in the community will usually have their requested features added first, but if you have any great ideas, please post them in the FSSCP Forum on the Hard-Light Productions Forums (Be sure to do a search first so you're not reposting ideas).
While the developers are hard at work implementing new features, a critical area that you can help in is reporting bugs and helping coders to track them down. The place to do all of this bug tracking is GitHub, the repository currently used by the FSSCP team. To learn more, please check out the article covering Bug Reporting
Release Timeline
Now recorded here: https://github.com/scp-fs2open/fs2open.github.com/wiki/History-and-Release-Timeline