EvilBivol-1

Здесь тоже много атмосферного: http://www.airplane-pictures.net/type.php?pg=1&p=149&order=screen_timestamp

Do you have Easy Avionics on by any chance?

The button press problem happens, because trigger conditions are cheked discreetly at a short interval (once per second or less). The trigger may not "catch" a down press if the button is released quickly, before the trigger condition check gets executed. Holding the button down for a moment resolves this. The only real solution is not to use button down triggers to check player input and where possible instead use triggers that check the output strings on the actual indicators. This isn't always possible, though, and anyway requires use of the game console, which is disabled.

Trimmer clicks!

Currently it takes one full turn of the trim wheel to move the needle 10 degrees. Of course, the model is WIP and this may change in the future.

Unfortunately, for a period of time our system was not processing messages sent by email. When the problem was resolved, all of the backed up messages were processed. This may be the reason you received a response now. If your problem is no longer applicable, you can close it manually on the support sites http://support.digitalcombatsimulator.com/ or http://support.lockon.ru/, or by replying to the email with the title and body text quoted.

Unfortunately I'm not sure what else you can do, except try to keep as much free RAM as possible for DCS. Turn down the graphics setting and maybe try closing some windopws programs before starting DCS.

Yes, it looks like your system is simply running out of memory (RAM) and is not able to load the missions fully. It's quite possible that this situation may have changed between patches as the game software is updated and changed. DCS works best on a 64 bit OS. However, there is a fix you can try to allow windows to allocate more RAM to the program... If you are on Win7 or Vista, try this: http://forums.eagle.ru/showpost.php?p=1084420&postcount=8 If you are on XP, try this: http://forums.eagle.ru/showpost.php?p=1092529&postcount=38

I have a feeling your system is just running out of memory and is unable to run the mission. As an experiment, try reducing the SCENES and VISIBILITY settings in your game options, as well as turning off civilian traffic and mirrors (if these are on). See if that makes any difference.

64 or 32 bit OS?

Given the continuing OT of the thread, and the lack of a better solution outside of deleting the starting post, which seems to be confusing or misleading readers, we are closing the thread. Understand that we have nothing against user age polls. Feel free to open a new thread to conduct such a poll, but take care to keep it focused on the subject line.

Worked here when tested. Try it to be sure and we can go from there.

In the View Cockpit category of input commands you will find commands to select different pan speed. Fast pan speed (L.SHIFT + ]), normal pan speed (L.CTRL + ]) and slow pan speed (L.ALT + ]).

Он, как раз со мной.

Это не наш Вагнер, хотя даже позывной тот же. :)

По поводу роликов тебе лично ответели как минимум два раза.

The same - mainpanel_init.lua. Check line 979. You generally only need two files to read everything non-digitial in the cockpit. Clickable elements (switches, buttons, knobs) are defined in clickabledata.lua. Non-clickable, non-digital elements (all needle instruments, analog counters, caution/warning lights, flight controls) are in mainpanel_init.lua. Reading digitial output on the displays requires the game console, which is considered a debugging tool and is disabled in the release versions. However, if there is a particular digitial element you want to use as a condition in a trigger (like the status of the TGP for example, or target range, etc.), you can ask here and I can try to help on a case by case basis. If you haven't seen it, we have released a short guide to using cockpit triggers: http://forums.eagle.ru/showthread.php?t=81376

It's been discussed before, but generally a combination of the debrief log and LUA exporting can provide enough data about the mission-end state of the world for a mission generator to re-populate it accordingly for the next mission. What is missing is a single application to gather this data and a mission generator that can use it to place units on the map. Theoretically you could even track destoyed world objects (like bridges, buildings, runways) and then blow them up again at the start of the next mission to simulate a certain level of persistence.

This might get a little complicated, so bear with me. Firstly, let's take a look at the Fuel Counter in the cockpit. It consists of five digits, such as: "05500". If you open the file mainpanel_init.lua in the folder \...\Scripts\Aicrafts\A-10C\Cockpit, starting on line 808 you will see how the animation of this readout is defined in the config files. You have three arguments - 90 controls the first digit (tens of thousands), 91 controls the second digit (thousands), and 92 controls the third digit (hundreds). The last two digits are not animated and always show "00". All cockpit animations are played on a scale of 0-1. So you have to convert the actual readout of the display into a decimal format. In this case, the actual readout is from 0 to 10. So, if you want the trigger to work when the first digit reads 5, you have to divide 5 by 10. Using this value (0.5), you can enter the Min and Max values into the trigger condition (such as "0.48" and "0.52"). In this case, when the animation reaches the set range (indicator in the cockpit showing '5'), the trigger will be activated. An example. To make the trigger work when the fuel readout reaches 05500 lbs, do the following: Once -> Cockpit Argument in Range (90), (0), (0) Cockpit Argument in Range (91), (0.49), (0.51) Cockpit Argument in Range (92), (0.49), (0.51) -> Message to all (or whatever)

We do value feedback and read the forums on a daily basis. Feedback is one of the many considerations that are critical in making product development decisions, but it isn't the only one and isn't necessarily the driving one.

Thanks, of course we can edit the FAQ to add some links. Personally, I think the wiki is the best place to organize community knowledge resources.

To be completely precise, it's a Rear Warning Radio. Meaning, it's not a passive receiver, but a small active radar. :) http://www.duxfordradiosociety.org/restoration/equip/aps13/aps13.html

We are working on increased traffic security for online play, but at the moment I can't say when, if at all, this might be available for FC2. I understand it's a sensitive issue, which makes it all the more important that everyone take an extra second to consider the manner of your posts and avoid derailing the thread toward a closure or worse.

Should be on pg. 13-11 of the Flight Manual. Check your controller input axes in the Input Options of the game. Use the Axis Tune button for each axis you want to tune.

Great you got it resolved.