FalloutNow!

Currently this map is the only one available since the game crashes when you cross the exit grid Razz. If anyone knows how to get the exit grids working properly, please let me know. I've followed the tutorials for exit grids but they still don't seem to work. I'll look at this more tomorrow to see if I can get it working, but if anyone is familiar with mapping, your assistance would be appreciated. You can feel free to load up the mapper with the scripts source attached at the bottom and the data directory above (note that the imarket.map is actually called "artemple.map" due to the FMF executable not yet working quite right).

I will be putting up daily builds this week with any improvements as they become available. If anyone would like to help get the map situation sorted out we would all greatly appreciate it. My expertise is definitely not mapping.

There will be a news post for the new build later today, but until then, here's the info:

FMF Demo Alpha Release Build 002

Download Location
http://www.fanmadefallout.com/project/builds/Demo/Beta_Test_Builds/Alpha_002/FMF_Alpha_002_data.zip

System Requirements
Currently we have confirmed that the demo should be playable on a clean install of Fallout2 1.0, unpatched.  If someone has it working on a patched version of FO2, please let us know so we can add this to our supported systems list.

Installation Instructions
1. Rename your C\Program Files\BlackIsle\Fallout2\data directory to "data.org" or "data2".
2. Extract the zip file above to C:\Program Files\BlackIsle\Fallout2. It will replace the original data directory.
3. Open the extracted data directory and set the "proto" directory to Read-Only.  Apply this change to all enclosed files and subdirectories.
4. Run the Fallout2.exe executable and start a new game.  After getting through the start videos, you will start at the imarket map.


Change List
-Fixed West exit grid on starting map.
-Added East exit grid to destination map so that user can return to the starting map.


Bug Reporting
Our Mantis Bug Tracker is available to anyone who wants to sign up and log defects they find in the demo.  Please keep in mind that if you find and report a defect we may need to ask for more information if we are unable to reproduce it or if we would like you to test the fix.

What NOT to report:
-Complaints or flaming, I.E. "Where are all the NPCs!" or "You guys sux0rs."
-Major feature requests such as new quests, NPCs, or adding mind-controlling aliens to the game.  Minor feature requests or improvements are okay, but we make no guarantee that we will implement them.
-Obvious missing elements that just haven't been implemented yet. Unless you have access to our private forums, you probably don't know what those elements are anyways.
Anyone who does not obey these guidelines will be warned and/or banned from use of the tracker.

What to report:
-Generic bugs related to maps, quests, scripts, dialogue, etc. Basically anything in the game that does not behave the way that it should.

How to Report a Bug:
1. Sign up on the tracker at http://fmf.filmchicago.org and confirm your account from your email address, then you can log in to the tracker with your username/password.
2. After logging in to the tracker, you will start at the "Main View" page.  If you have reported any past defects or have anything assigned to you, it should be displayed on this page.
3. Click the "View Issues" link in the top menu to be transported to the bug list.
4. Do a search for the bug you found to see if it has already been entered.  If it is already entered, please do not re-enter the same bug a second time.
5. If there is no bug logged yet for the issue you are reporting, click "Report Issue" in the top menu to create a new bug entry.
6. In the bug report page, fill in the fields with as much information as possible:

• Category: The category which the bug falls under such as Art, Dialogue, or Maps.
• Reproducibility: How often does this bug occur?  If you can reproduce it 100% of the time, choose "always". Select an appropriate choice for the reproducibility of the bug.
• Severity: How big of an effect does this have on gameplay?
• Product Version: The version of the demo you were playing when you found the bug.
• Summary: A short description of the bug. This should be very brief and include keywords for the bug, such as "Crash when initiating conversation with Stockley."
• Description: A longer description of the bug.  This should be detailed and describe exactly the symptoms of the bug and a summary of what causes it (if known).
• Additional Information: In this section, please enter the steps to reproduce the bug in a numbered list.  Try to keep it to as few steps as absolutely necessary to recreate the bug.
• Location: For the demo, this should always be COTC.
• Subcategory: A more specific identification of what specifically the bug affects, such as an Item, a Quest, Scenery, etc.
• Difficulty: This is for development purposes only and you do not need to complete this.
• Upload File: If you have a screenshot, log, or other file that would be useful in troubleshooting the bug, upload it and attach it to the bug.
• View Status: This should always be set to public.

7. Finally, click [Submit Report] at the bottom