Zeke

Definitely a great time on the server tonight, thanks for hosting Bull. Looking forward to many nights of gun fights over the virtual Korean skies.

What's the name of your server Bull?

I totally agree. The smudgy dirt or whatever makes it very difficult to keep your eyes on targets/planes near the ground. I would rather have a clean canopy.

Got it, Thanks! Didn't know about that function before that will save a lot of time in the future also.

Thanks for the responses guys. I found the Gun-Missile switch in the Controls options and was able to map that to my homemade panel. Still can't find the canopy switch in the controls options to map that. I tested the taxi thing even in take off missions where the plane is ready to go I have the problem with it moving and the noise.

Yep, still no change after reading that post. I can't move anywhere till the power is at around 80 rpm's. That and the noise don't seem right. I'm sure I'm doing something wrong.

Hi, I'm going nuts trying to figure out what I'm missing/doing wrong. After starting up the jet and doing all the checks and calling for ground power 'Off', I go to taxi and it takes a great deal of power to get the plane moving. When it does move it makes a grinding noise like it's dragging something. I hit the 'W' key and I have the toe brakes mapped inverted to my Saitek rudders. Is this normal? It doesn't seem to be and I don't notice this in any YouTube vids I've watched. Help. Oh, are the cockpit canopy 'Open/Close' key and the Guns/Missile/Off switches able to be mapped? I looked all over and can't find them. Tried a few that look like they could work but no dice. Ciao

Picked up the F86 F, Wow! I love this bird.

No problems here after several attempts. Plane just noses over and no problems with the engine.

Ummmm, all this is interesting. Lately what I've been doing is leaving the rad to auto and just maxing out the engine at 2800 rpms and 1.8 ATA in combat. Haven't had any problems with the engine failing.

Thanks for the input guys, I was just really confused after flying IL2 BOS so much. I was in the habit of really keeping an eye on my ATA so I didn't kill the engine.

After reading about the K4 in the DCS manual and watching YouTube vids and reading whatever I can find on this form, I have a few questions regarding engine management. I can see in the vids that most of the guys driving those 109s are maxed out at 1.8 ATA and around 2800 rpms. According to the manual that would damage the engine shortly. I was trying to keep my ATA around 1.35 while practicing. I tried just maxing it out and didn't have any problems. Should we be concerned with keeping the ATA limited? What is more important to keep an eye on, RPM or ATA? I've read also that as long as the MW50 is on you don't have to worry about ATA? Love this flight model!!

Jack4, have you edited your axis settings? Try using a steep curve of 30 or more to start off in the x and y axis. Without any editing I find the planes very difficult to handle.

Thanks, after reading a ton of this stuff I found what I was looking for. I downloaded the data.lua file and edited some stuff that I needed in the Su-27 folder. Pretty easy once you figure out what is going on.

I've looked around and I can't find where the info is on how to edit a lua file for key commands for a homemade panel. I had it all for the A10c put all of joystick and panel commands have changed since I last played this sim. Can anyone point me in the right direction to get the info I need in order to edit the lua file. Thanks

Anyone using a TM Cougar with the Su-27 or FC-3? Don't know if my old LOMAC profile will work. Can't wait to fly this 'new' bird.

I unhooked the USB monitor that is working and plugged it back in, no problems, it came right back on and worked fine. Changing resolutions didn't do anything. When I push the detect button a blank monitor comes up and says 'another display not detected.' Not sure if that means anything or if that's just a default message. Thanks for helping.

I tried other USB ports and when I did, windows loaded the drivers and said it was ready to use, but it stayed off. I don't have another computer to try it out on.

Hi, This happened a couple of weeks ago and I've tried finding information everywhere I could think of to help fix the problem. I'm at a loss. Here is what I have: Two 8" Lilliput USB monitors, with TM MFD's. Everything was working great for a year and then one day both USB monitors turned off and went into standby mode (little blue lights in the lower right hand corner blinking). This happened while I was flying another sim that I don't use the monitors in. I turned one of them off and turned it back on, this usually fixes any problems as all my monitors turn off and then come back on. Only this time the main monitor and the other USB monitor came back on but the one I turned off stayed in standby mode. I got up and unplugged the USB monitor then I plugged it back in. No joy, still wouldn't come back on, it just stayed in stand by mode. I then rebooted, still the same problem. I updated the Link drivers, still no joy. Anyone have any ideas? Using Windows 7.

http://www.cubpilotshangar.net/page105.html Not sure why your stick isn't working, but this site may help.

http://forums.eagle.ru/showthread.php?t=65998 This link got me started last winter. I was able to build one generic box and a UFC box. I had never done anything like that before. Much Fun! Good luck.

Hi, yes it is a bit twitchy for me also. I have a evenstrain mod so it even more so. I use a 30 curve for the Hog for both pitch and bank. Without doing that I couldn't handle it too well. Start with something and experiment what works best.

Check out Viper's files, they are the best I've seen. I don't have a link, do a search, should be easy to find.

What do you guys recommend to set the file sizes at? When I go into the options for virtual mem and try to set it manual, I see an "Initial" and a "Maximum" setting.

Yes, I have the same problem since 1.2.6. Never had a crash before, ever, then after the upgrade to 1.2.6 it crashes almost every time I fly it. I have tried a few things to hopefully fix it to no avail. Hopefully the next patch will fix this.