Sinky

The noise from the radio might have something to do with the warning sound they added if you tune your radio out of range or something like that. I've also tested another 4 GBU-12's and they all hit spot on the laser, only thing I noticed is that the GBU-12 seems to lag for the first meter when it comes off the rail. Arming levers are usualy on the left side of the seat from my experience, least it was on the F16.

Take a look at page 158 in the flight manual. Read the section about the pinky switch. When you start off the pinky switch is in the center position I think which will cut out most external lighting. Edit: I usually use LCTRL + P to allow me to turn the lights on and when I'm in the air and about to ingress I cut them with LSHIFT + P.

I've only dropped one in the final. Now you have to go into the profile and turn auto-lase on if you use it, turned off by default now it seems. I dropped from 9000ft since I figured if it's accurate there then it should be at the usual 10000+. It hit smack bang on the laser, did a quick markpoint test also using point mode it was bang on. As someone has already said, it doesn't wobble nearly half as much now.

Anyone else noticed the metalic shine on the aircraft in some situations? It's also on the flight instruments, looks nice. The aircraft seems faster to me and the game runs well enough to get me by till I upgrade this old 8800GT around october. Great work on the menu music also.

That's what I did, having to download the setup-3.bin from FTP 3 though. Only 3 mins left on the last file. :thumbup:

Now I've managed to get onto us ftp 1 after frantic clicking I'm getting 450kb/s. Really can't wait to drop some CBU's for the first time and use that cannon without the lag.

Well theres a kick in the gentleman vegetables. If I actually manage to get it downloading from the us ftp I get around 20kbs at best, compared to 200kbs per file on the german ftp.

I think it is modeled, I've had warnings on both MFD's saying something along the lines of "EO Time" which went away as soon as I switched the EO off. Guess if I kept it running longer I would have toasted the mavs. Maybe the warning is modeled but the heat issue is not, I like to believe it is though.

That post was directed at the origional poster. Try adjusting the brightness of the NVG. Also if your not using any antialiasing then that might be the problem, I can barley see it without AA. If that doesn't help then I have no idea, sorry.

I got this working correctly earlier. I used the MQ-9 for AFAC, setup his freq and targeting data. Make sure it's day time also, at night the MQ-9 will mark with IR pointer.

Yeah, as I said on the 104th server earlier on ( name Sharpie ), I tried changing the lodadd to 0 and it worked fine. Thanks for the help.

Can't wait. :thumbup:

They're going to release the DCS A-10C in the same way they released the DCS Black Shark, same simulation level, maybe even better. It's not going to be in flaming cliffs 2 as a flyable aircraft, but you should be able to fly it with people who use flaming cliffs 2 just like you can with the ka50, as long as you own the A-10C. Edit: Frederf beat me to it :)

Problem fixed, I'm sure I tried changing the vis distance and it didn't work, this time it's working on every setting but low. I'm 100% sure I haven't edited the graphics.cfg file, but I'm sure that lodAdd is not supposed to be set at 100 for low vis.

Vis is set to low and I use high scenes. Graphics config is untouched default, but i'll post the section your looking for just incase. Camera { current = "Medium"; Low { near_clip = 0.2; middle_clip = 5; far_clip = 140000; structures = {30, 2000}; trees = {1000, 3000}; dynamic = {300, 20000}; objects = {3000, 80000}; mirage = {3000, 20000}; surface = {10000, 50000}; lights = {50, 10000}; lodMult = 1; lodAdd = 100; } Medium { near_clip = 0.2; middle_clip = 5; far_clip = 140000; structures = {40, 4000}; trees = {1000, 6000}; dynamic = {300, 20000}; objects = {3000, 80000}; mirage = {3000, 20000}; surface = {14000, 80000}; lights = {100, 30000}; lodMult = 1.5; lodAdd = 0; } High { near_clip = 0.2; middle_clip = 5; far_clip = 140000; structures = {60, 6000}; trees = {1000, 9000}; dynamic = {300, 20000}; objects = {5000, 80000}; mirage = {3000, 20000}; surface = {20000, 80000}; lights = {200, 80000}; lodMult = 1.5; lodAdd = 0; } }

Haven't tried that, I'm running 197.45 ( few months dated ) on an 8800GT. I'll get the latest drivers put in later tonight see if it makes any difference. Thanks. EDIT: Turns out the 197.45 drivers are actually the newest ones.

Hi, having some issues with the new Su-25 model, this has happened now on two completely clean installs. The only way I can describe it is by saying it's as if the low poly lod is mixing with the high poly model. I've searched all 30 or so pages of the bug thread and found nothing on this issue. Like I said, clean installs, no graphics or fps tweaks made apart from setting water to 0. Here's a few screen shots to show what I mean. Take note of the wheels, engines and the mid section of the fuselage on the top. http://i952.photobucket.com/albums/ae3/sharp1e/b6926d5b.jpg http://i952.photobucket.com/albums/ae3/sharp1e/3f3aba3d.jpg http://i952.photobucket.com/albums/ae3/sharp1e/594e0dc8.jpg Hopefully someone knows a solution to this problem, I love flying the Su-25, but this glitch makes it look ugly. Yes I know I still need to setup my pilot logbook on the new install :).