Deezle

I actually just read a post from a former Viper pilot on another forum yesterday.

Agreed, seeing little electric passenger trains running where diesel freight trains should be running is a bit odd.

Yes, above 20k it's crazy right now, you can put it totally vertical in burner and it will accelerate well past mach 1 to well over 70k.

The M-2000C is quickly becoming my favorite module. My only real gripe so far is lack of mapable controls. I took some of the keyboard only ones and made them usable on my joystick/throttle/panels, but lots of stuff (the radar controls most notably) is not mapable yet. I also find it a shame that the (real plane) designers limited the slick mk82 to CCRP only, CCIP with mk82s would easily be the most accurate delivery of unguided bombs, no matter what it seems there's always a silly compromise made :( I'm really loving this plane and can't wait for more updates from RAZBAM!

I would agree that most contacts end up way too close to the center of the display, making it very hard to tell whats going on. I would think there needs to be a small, virtual circle in the center of the display where contacts cannot move any closer.

Seems like the line you added has some extra stuff. Try this at the very end of the file.

Thanks, works great :thumbup:

I've found the M2000C to be VERY susceptible to crosswind on takeoff, even a slight breeze damn near pushes it all the way off the runway. My toe brakes are properly configured. No other plane in DCS is pushed around this badly on takeoff.

I've experienced this occasionally, my textures are always set to high. Sometimes all the traffic is grey.

The terrain color in Nevada makes the FLIR work much better.

The throttle(s) need to be all the way down before it will let you move them out of cut-off.

The pinky switch on the left throttle needs to be in aft position for the anti-collision lights to work.

This video covers the SPI. [ame] [/ame]

I watched your track. You never set the TGP to be your SPI generator, therefore you dropped the bomb over the steerpoint which is the SPI by default.

I don't think the GBU-12s even begin tracking the laser until ~15 seconds before impact, they certainly don't appear to be anyways. Make sure your TGP is SPI, if you're releasing where your steer point is and not where the TGP is pointing, you'll never hit your target. Yes, SPI, not SOI, brainfart.

The GUI size needs to be the size of all 3 monitors to work in 1.5/2.0. Annoying, but it is what it is for now.

I've never had a Tunguska shoot a missile down. The Tor will though.

You need to bind a zoom axis or at least use the assigned keys to zoom out (increase FOV).

You do have a zoom axis bound? I use a single screen profile and it works for me.. I also changed this line to cover all my bases, perhaps you need to do it as well. function default_fighter_player(t) local res = { CameraViewAngleLimits = {20.000000,160.000000},

Server.lua file found in the DCS/config/view folder. Find the KA-50 line, under CameraViewAngleLimits, change the bigger number to a bigger number (120-140 is the default IIRC, I like 160)

Same.

The new default map textures in 1.5/Black Sea map make it very difficult. I've found it's much easier to spot things in the TGP in NTTR. You may try an alternate map texture pack such as Starway's Northern Europe texture pack.

Yeah lighting from a distance needs (and always has) some work. Get a few miles outside of Vegas and you can't see any lights, very distracting. Aircraft lights are the same way.

Yes, this has always been in DCS. Most servers are fine but I did encounter one today that didn't allow my modded FOV. I'm trying to remember which setting/file it is that the host needs to change, but can't remember at the moment. This is quite annoying because it basically makes it unplayable for us on some servers and the host likely has no idea they're doing it.

I managed a landing after losing one wing and both wings, but yeah, most of the time it's pretty much uncontrollable.