This is a list of the problems I have found so far. It is mainly for Sudz, but anyone can feel free to chime in.
1. Spawn LocationNo matter which flight of the mission you choose, your plane will spawn with the first flight on the field, separating you from your flight temporarily until you roll on over to rejoin them.
2. Cannot takeoff from more than 1 base correctlySay you have FlightA taking off from A1 and Flight B taking off from A2. If you choose to be part of FlightB and launch, your plane will take off with FlightA, while the rest of your FlightB takes off from A2(which takes us back to problem 1 above).
3. Inviso-planesIs there a set number of AI that are allowed to be visible on-screen at a certain time? In larger missions, invisible planes have been giving people problems. In my Raiders mission, the enemy doesn't appear with icons until the 2 sides are about 500ft. from colliding.
4. Cue Card EventI have yet to get this to work. Ok, you put an event in as a cue card event. selecting Cue Card in the event choices and using a .txt document for the words. Now, do you select a move time for how long it is up? If not, that leads to the next question. The event to bring the cue card down. Ok, you set another event and choose Cue Card Stop. To bring it down. do you select a start time for Cue Card Stop, or is that in the move time for Cue Card? And that's not all! Alright, we have an event for Cue Card Stop, which by definition should bring down the cue card, HOWEVER, what is the check box in the event properties called Stop Current Cue Card used for then? Do you check it? If so, then why have a Stop Cue Card event? A step by step by someone in-the-know needs posted on this one.
5. Foo fightersIf a friendly flight is within dot range, but out of icon range, those dots will fly any way but forward(usually backward for a little bit, then warp back forward to restart the backward motion. Only appears to happen with friendly flights.
6. The dreaded .res fileAnyone who was there for the opening week or so of my Raiders mission, knows the grief I went through with this. I modeled the setup based on the default 1vs1 mission, as it contains a .res with one sound event, mine had more though. I successfully created the .res, but when people flew the mission, it would crash the game. Others along with myself tried everything to fix this, but could not. In the end, I had to include the folder containing all the sounds with the mission download. I chose to tell the mission to look for the events in Missres folder, simply because I knew everyone would have that folder. It works, but anyone who doesn't have AH on their C: drive (which I do) has to go in and change all the events to look in the correct drive for their pc. Not hard, but a pain in the arse since the .res is supposed to take care of this.
Sudz, or anyone else, could you please post a simple mission containing at least 3 sound events with a working .res file and instructions on how it works correctly? If you have my Raiders mission, just take the sounds out of there, as they are already in the correct AH format(PCM 22khz 8-bit mono). I have yet to see any working .res file for a mission besides the default.
Thanks all for reading and if anyone has anything to add, disprove, whatever, please chime in. All I ask is for actual mission proof if someone disagrees with this stuff. I can provide film/screenshots if need be.
EDIT: Almost missed a couple.
7. Sound Event ProblemIf you have a sound that you assign to play for each flight on the same segment at the same event start time, when the sound plays, it will "echo" horribly, as in you here the sound for each flight playing about 1/4 second apart, which sounds like inaudible crap. Only seems to play the overlapping sound if you set it for the conditions described above.
8. Briefing room problemI created the map Missn2 for offline missions, which contains custom airfield that do contain a briefing room. When starting a mission on this map, instead of the brief starting looking at the curtain, it starts off looking at the pilots sitting on the right side wall. I went back into the T.E. and rotated the Briefing Room object 90 degrees, hoping this would fix it, but it made no difference. This only seems to happen with custom airfields, which isn't a problem for most, but for me it will hinder future custom map-for-mission projects if we want to use the Curtain Opening event.
