Sinky

Here you go. PrecompiledEffects { mode = "USE_PRECOMPILED_EFFECTS_FOR_UNCHANGED_FILES"; }

Haha yeah, I'm glad you like spooling up whilst airborne ;).

Wouldn't let me attach it, would you like me to zip it up or post a particular section here?

:music_whistling: I cry innocence. I never fiddled with anything when I first put it in, just dropped the file in and I never saw the blur or the noticeable bloom effects.

Part of the fun comes from setting up your weapon profiles on the ground, I usually do this while I'm waiting for the INS to fully align.

Screen shot attached using 2x AA. I also noticed in beta 4 there was a haze.fx in the haze folder but in final the haze folder is empty, this have anything to do with it?

I cross checked both the hdr.lua files for any differences and there were none what so ever.

I will provide a screen shot shortly, maybe I'm failing to spot the difference but the blur should be pretty easy for me to spot.

I've done this but with my own hdr.fx that I got from my old beta 4 install. It doesn't seem to restore the blur feature for me though... Wish I could have that effect back because sometimes I don't run with any AA and the blur makes the game look less ugly. Also mucked around with the 'bMag' in the hdr.lua and haven't seen any noticeable effect.

Regarding the JTAC datalink. If you input group id and own id of 01 while on the ground, the game will reset it after you take off and you will have to set it again.

Would it not be MM 17500 32000? I'm not sure but I think he may have dropped the 0 from the end of his coords. I usually receive 6 digits. In which case you would enter MM175320 into the CDU.

I see, I haven't tested it myself but I've heard if your low enough they will shoot at you with small arms fire. There also buggers to kill with the gun so I usually carry one rocket pod beside the jammer.

You can area designate or point lock, both will work as long as you set the SPI to the TGP. Switch to your maverick and you will notice once slewed to the SPI it will have the target in the center but it will not have the target locked and this is why you can't fire. You need to manually lock the target and you can do this by slewing the cursors around like a madman or you can simply keep pressing TMS Forward Short ( with the maverick as SOI ) until you see it achieve a lock. If I'm still confusing you seeing as I'm not the best at explaining things then let me know and I'll refer you to one of Tyger's videos showing how to do this. Edit: Here's the video anyway seeing as I'm going off for tonight. Instead of pressing and holding LCTRL+Up like Tyger says just give it a short press and it should lock providing the seeker has a decent image. http://www.youtube.com/watch?v=25MgpCEe114&feature=related

Once you have the mav slewed to the SPI you set using the TGP you need to lock the target by pressing TMS Forward Short, if it doesn't lock, get in a touch closer and try again. If you look at page 84 in the manual you can see a table showing what effect the TMS, DMS and all other control stick switches have depending on your SOI.

:huh: Infantry is modelled.

I know, I was just messing. Haven't got access to the other pc at the moment so I will check the page count tomorrow.

How come I downloaded it the other day on another computer so I could print it out and I'm nearly sure I had the current final? If you check page 29 there are pictures showing each squadron's paint scheme, I don't remember seeing this in the beta manual at all but it was in the one I downloaded on a separate computer. If I'm just being an idiot then I apologise :).

Yes :).

This numpty forgot to save the track :doh:.

Sorry to steal the thread but it's kind of related. Just played the Smerch Hunt mission and my first two mav's came off the rails fine ( one D and one H ) but the last two wouldn't fire with a successful lock. I checked the DSMS and neither would ready up at all. Yes I was fenced in seeing as the other two and the CBU's came off perfectly fine, anyone else experienced this? Either the mission is bugged, mav's can fail or I'm an idiot.

I still don't understand where I might have said what you think I said. Check who he quotes in his #42 post, he did not quote me. That's the only thing I can see that makes sense. Edit: You may mean why did I respond telling him how to use EXP mode, that was because I never actually read the quote in his #42 post, I just saw him getting confused by the EXP mode so I tried to help.

I wonder if there are any funny comments hidden in the code, seen quite a few in my time where the developers got annoyed.

I thought he wanted to know how to cycle the EXP modes on the TAD? I thought I would help him by giving him the key command for it in case he wasn't a HOTAS user.

+1. Probs a combination of C and C++.

I would advise against using labels but you should be able to edit them in the same way you do in FC2 using the labels.lua. I haven't tested if it works since I don't use labels but it very well could have been changed in A-10C. Lonecrow66: The keyboard command for that is "V" by default, switches between normal, exp1 and exp2.