posted 01-22- 09:33 AM
After many many hours and hundreds of mission sends I came to realize that at times you would have the same mission as the host yet for some reason SDOE would find a mission conflict and request an overwrite. Mission sends work well in SDOE but cause a few problems including delays and desktops.So I have assembled approximately 250 multiplayer missions in a 258kbyte parfile. It contains most of the popular mission and some lesser knowns (some of my creations I haven't hosted frequently). This will give everyone common versions of the frequently played games.
Get it here:
Multiplayer Mission Pack
Note: Read the included readme for directions. You will have to remove duplicate missions from your multiplayer folder for it to work properly. I would recommend copying the multiplayer directory and then removing all your missions in the original multiplayer directory. Then add back missions you don't see that you want to have.
Mission writers: Please send me any updated missions that don't appear consistent with your creations or that you have added and want to have included in future packs.
Why did I do this for a couple of reasons:
- The big one: Desktopping. Most of the time desktopping occurs when a mission is being sent by the host. This often becomes frustrating for others who have the mission and are waiting to start a game.
- Last minute game entries. How many times have you been just about to start a game when a new person joins without the current mission. With a common pack these last minute entries will come in with the mission ready to fly or if the game is full, a new mission can be quickly loaded without losing a bunch of guys who've been waiting for 10 minutes.
- Game creation delay. With over 250 missions in my multiplayer folder I found a big delay when entering a game or hosting a new one. This often caused desktopping as well. With the parfile the mission detection is quicker.
- Convenient way for new players to gain access to the most common multiplayer missions.
- Mission organization. The pack seems to keep the missions grouped more logically. It's a little easier to find the right one now.
I have called this a beta not because it doesn't work. It does, Spyder and I have been using it for the last few days and have not been sending missions to each other (with the exception of one that wasn't in the parfile - which I desktopped for five minutes to get). However, I don't think I have a complete compilation of the current mission versions and plan to add to the pack over time.
Also the missions included have not been reviewed for spelling errors, goofy objectives and other aspects. There may be some that contain unusual squadrons (for example the =FC= squadron - which may cause a mission desktop on startup). I will be reviewing the missions over time to remove these unusual errors.
I can't predict how people will respond to it. So check it out. If you like it I'll work to add people's favorites, updates and new missions that include updated planes and terrains (if desired).
I also want to determine the best size for the pack. At this time 250 missions is probably too big. Unfortunately it's hard to decide what to take out. So I went for completeness. (I went with 250 because I always seem to have that many in my multiplayer folder).
250 is a little big because if a player tried to join a game just set up he will often desktop until your system has loaded the mission info. To avoid this players should wait ~10 seconds before joining a new game - this is a good idea with or without this pack.
These are creations of the community and I don't take credit for them. Thanks to all who have written these missions, they have helped make SDOE stand out among flight sims.
Get it here: http://tailslide.firelight.dynip.com/Files/Mission%20Pack%20v0.99%20Beta.zip
Thanks Tailslide for making it available.
Spin
[This message has been edited by spin (edited 01-22-2000).]
[This message has been edited by spin (edited 01-22-2000).]
[This message has been edited by spin (edited 01-22-2000).]
[This message has been edited by spin (edited 01-22-2000).]
[This message has been edited by spin (edited 01-23-2000).]