Baggy MacDouche

I don't think it is a bug. I think it has something to do with using the DMS to cycle weapon profiles. It will select the default profile unless you manually select the saved profile from the DSMS. Something like that. There's a thread about that somewhere. Yeah big help I am. ;p

The GBU-31/38 profile page won't even have settings for LS Time available. Also, if you happen to make a mistake in the scratchpad or input an invalid entry, you will see the message, "CICU INPUT ERROR" at the bottom of the HUD, as well as the CDU. If this happens, press the CLR button to clear the scratchpad entry field and start again.

I committed the entire manual to memory. :p

Great info Azazel. This is the kind of stuff that I really need to work on. Any tips on dealing with manpads?

I have found that once mark points are set*, the Mav is SOI, and the china hat Aft Long has been initiated to slave to steerpoint, then from then on, as long as I don't change the SOI or slew the mav sensor, all I need to do is cycle the mark points and the next mav will automatically slew to the next mark point location. I think the key to this might be that unless you use the mouse to click on the UFC rocker to change mark points(or have it mapped to your stick directly), you will need to make the HUD the SOI and use the DMS L/R commands to cycle mark points. I believe this will break the mavs slave to steerpoint. I'm not 100% on this point though. This also works for the tgp of course. For example, lets say I set three mark points for one target each. After the run in and quick draw of the three mavs, I'll set the tgp to SOI and slave to steerpoint. I can then cycle the mark points starting on the first target fired on and watch as each mav impacts and then switch to the next mark point, etc. *With this method, you want to give the next mav's sensor the best possible profile to detect the target. The more accurate you can make that mark point location the better. That way, when you cycle the next mark point and the mav sensor slews to it, it should be good enough for the sensor to create a "picture" and lock onto the target once you hit TMS-U-S. You should never have to set a SPI or slew to an SPI with this method. It relies solely on mark point information and the mav's ability to identify and lock onto the target.

Since the UFC rocker is mappable, I set them as shifted DMS L/R. I use the small pinky button on my warthog(normally NWS/LAS) as a modifier. I've gotten pretty good at doing recon and setting mark points. That way I don't have to touch the TGP at all when I am on my attack run. I use the laser to designate mark points, trying for a spot on the ground below the vehicle. This helps ensure that when the Mav is slaved to steerpoint, that it is going to be pretty accurate. With Mav as SOI, it's just a matter of selecting the mark/steerpoint, TMS-U-S, rifle, then without having to take my hand off the stick, use the shifted DMS to cycle markpoints, TMS-U-S, rifle, repeat. The Mav seeker seems to do a pretty good job of acquiring the target without having to get more precise with the TGP, but using the laser in area mode when creating the mark point is key. Oh and Strong...don't you dare go anywhere. :)

Just had to pop in and tell you Deadman how much I am enjoying my new warthog covers. Got them much faster than I expected too. :) Normally, I don't care so much about dust and such. A quick blast of compressed air would be enough to get the cobwebs off my gear. But since I've gotten the TM Warthog, I just couldn't bare to have so much as a spec of dust on these babies. They look great on my desk and love the remove before flight tags. Nice touch. I used to have to unplug my throttle at night because the lights were too bright(computer is in my bedroom). The cover blocks the light out completely. Anyway, thanks again. Great product that ever Warthog owner should not be without!

The last time it happened to me I was doing one of the campaign missions from the first campaign. I don't like the fact that the load-out they give to start is a few measly mavs and no tgp, so I would load an anti-armor load-out with 65Ds and CBU-97s and then reload the dsms. Mind you, this was the mission where I had already fired off a few mavs before I wasn't able to release any more. I have a feeling that the timer had gone long. I usually just ack the message as soon as it comes up out of habit because I, for some reason, thought that it didn't really matter. One thing I did not try was to power it off and then back on again. I wonder if in real life, another 3 minute power-up would effectively cool it down enough to prevent damage. Anyway, this will be the first thing I will try if it happens again. p.s. I didn't know about the laser burning out either. Will you get any kind of error when that happens? Will the "L" still flash when activating the laser even if it is not actually working, and will recycling it make it work again?

Been looking around for answers but nothing is jumping out in search. I know it has been discussed before but I'll ask again. Will the Mavs eventually malfunction once you get the EO Time message? I thought I read somewhere that it is just a warning, but that nothing will actually happen if the sensor isn't powered off(in the game). The reason I ask is I have encountered an issue with mavs a couple times now where no matter what I do, I can not launch a Mav. I was able to earlier in the mission and didn't change any settings or anything. Went through all the regular target acquisition steps I normally do, but when it came time to release the weapon...nothing. Release cue is flashing, etc. No error messages in the MFD, etc. The only thing I can think of is that I had the Mav powered on too long and it broke. Maybe not. Is there anything else that anyone can think of that may lead to this outcome? I don't have a track to post right now, but will try and get one if I encounter this again.

There is a reason that there is a big old hat dedicated to trim on the warthog flight stick.

Are there other servers to connect to other than what shows up in the server browser? Maybe it is the times that I'm playing but there don't seem to be many populated open servers. Even the ones that are locked usually don't have more than a couple people in it. Where are people playing?

I feel a bit guilty using a mav to take out a manpad sometimes. :)

wrt mark points, is there a way to delete them?

This is going to be awesome. I play almost exclusively with my Logitech G35 headphones with Dolby 7.1 surround sound. They already sound great. But surround sound plus cockpit shadows is REALLY going to add an extra dimension of immersion.

You're right. This is how I should be doing it. In theory, once the mav is slaved to the SPI which is set to Steerpoint, I could step through the points and use china hat fwd short while in the HUD to switch SOI to MAV. I could be mistaken, but it doesn't seem that there is a direct way to cycle steerpoints while the MAV is SOI. You seem to either have to be in the HUD or use the rocker on the UFC. Anyway, thanks for your help Bartleby

Is this the method everyone is using? I just want to make sure I'm doing it right and avoiding any unnecessary steps. I do the following. (TGP in LMFD, MAV in RMFD) 1.Find target in TGP 2.TMS-U-S until point track 3.TMS-U-L to set SPI 4.Coolie hat R-L to make Mav SOI 5.China hat F-L to slave Mav to SPI then usually I have to 6.China hat F-S to narrow FOV 7.TMS-U-S to track Cursor flashes when in range and within cone of influence. 8.Rifle! Am I doing that right? I've also been practicing using mark points to set up runs with multiple mav launches. This is the way I've been doing it. 1.Find target in TGP 2.TMS-R-S to set mark point Repeat 1 & 2 for other targets Start run in 3.With HUD as SOI, set steerpoint to first markpoint 4.Coolie hat R-L to make Mav SOI 5.China hat A-L to slave to steerpoint 6.China hat F-S for FOV 7.TMS U-S to track 8.Rifle! 9.Repeat from step 3 for next targets Again, same question. Is there another way I could be doing this that may be easier?

Thanks for the info guys. I guess I hadn't quite grasped how the SPI worked. I have been under the notion that I kept having to TMS-U-L every time I wanted to designate a target or a spot on the ground, etc. I didn't realize that info was continually being updated. Makes sense now, duh. :)

Late to the party, but I'm in the same boat. Problem started only after 1107. HDR is enabled. 6950 card stock(anyone want to point me in the right direction to unlock shaders?). Can't recall what drivers I'm on and I'm not home right now. Pretty sure either 11.2 or 11.3. On top of this issue, I'm also one of the ones who have encountered the 1 sec freeze on explosions, and I've noticed a bit more stutters than 1106. That version was working pretty much smooth as butter for me at very high settings. I should probably do a clean vid driver upgrade and a clean install of 1107. I know it won't fix this problem, but maybe the other freezes. Hopefully they can find and squash this one for 1108(or hotfix? :))

I'm going to ask another of my million and one dumb questions. Can you set a SPI while the TGP is masked? Or let's say that I am orbiting and I've gone into point mode on a target but have not set it as SPI before it starts getting masked. Will TMS-U-L still work, or do you have to wait until the mask is clear. Also, it seems like some times there is a M on the TGP, but I can still see the target just fine and no part of the plane is visible. What's going on there?

A bit off topic perhaps, but while I can understand why a lot of airfields don't have ILS, but why can't they have PAPI lights?

You are smart, I am dumb. That is all.

Is there a way to use the cursor in the TAD to set a point on the map as your SPI? Just an empty point on the map that say, you suspect there might be a target? I was trying this using the TMS up long yesterday, but it didn't do anything.

Definitely going to do this as I suffer from some freezes(first bomb too) and have noticed some white boxes and other flashes that I didn't have on 1106. I didn't change any settings between the two and I have a pretty high-end system. I'll probably manually backup my saved games folder, but from what I'm hearing, the files won't be touched on an uninstall? What about after the clean install? Does anything need to be done with the files to make sure they are working? I'm specifically interested in the input settings.

That's what I don't like either. Why isn't there some sort of option to start each mission at the ramp or runway. It seems that most of the SP missions all start either on the runway or in the air. I like having to do a cold start on the ramp and wish I could do it more often.

You know, when I watched that this morning, I totally missed the fact that there were cockpit shadows(hence 1.1.0.8). They just look so realistic and "right" that I didn't notice. :) I have a question about what was shown in the video then. Has the ability to hand-off targets to your flight using the SPI broadcast always been available? Or was it added in 1.1.0.7? Or is it going to be added in 1.1.0.8. I realize that the ability to do so in multiplayer was fixed in this last patch. I'm just not sure on the history of the SP since I'm still pretty new.