golfsierra2

Is there a final version available yet ?

I got the first 100 $ !! Do you think, my local banker will lend me the other 4.949.900 $ if I trade in my 2006 Honda Civic ?

Wouldn't that give a nice target range, too ? And how about crop circles at all ? Never spotted one when I was flying over the Crimean Peninsula... It would be a nice mod :music_whistling:

Gopher is working on some bombing ranges for A-10 training missions. This looks very interesting, and the topic was not covered before: See the whole discussion here: http://www.modern-air-combat.de/index.php?topic=2791

One could overcome this delay or at least shorten it significantly by having the TX parts active all the time, but sending the output signal into a dummy load instead of the antennas. I was I-HAWK TCO some decades ago, and we had our tracking radars and ROR in STBY, meaning the output power was only sent into the antenna when you switched from STBY to ON.

I should be calculated from - the ECM pod transmitting power - your radar transmitting power - the distance between you and the opponent - the RCS of the opponent's aircraft

You also may want to see this tutorial http://www.virtual-jabog32.de/index.php?section=downloads&subcat=37&file=793

I don't use free-track but TIR. AFAIK, both work similar. In your view.lua under Lock On/Config/View check this entry CockpitMouse = false It might read CockpitMouse = true and then your views are controlled by mouse. To let free-track take over, set the value to 'false'. Please post if this has solved your problem, others might looking for an answer, too.

After re-reading all the suggestions in this thread, I think that maybe the config.lua may be corrupt. Try to swap it with a working one. You find it at Lock On/Config/network/config.lua It may appear OK when opened in the editor, but maybe it became buggy somehow. The well known chat-bug that occasionally appears with this lua indicates, that Lock-On sometimes is doing strange things to this lua, for whatever reason.

Same problem (no connection) with the same software environment ? Give some more details: OS Lock-On / FC version Router Firewall

Sorry, but you won't see the tracks or videos of the flights online until the race is over. This is to protect the techniques / know how that the pilots developed in order to gain a good result.

It's correctd now.

All times of all pilots were measured this way: - start Lock-On - display Lock-On internal mission time (CTRL + Backspace) - load track file and start it - press "S" when the forward movement of the aircraft becomes noticeable - write down the time (for example 3.522 sec) - press "S" again to resume flight - press "S" when after landing, the forward movement of the aircraft has stopped completely - write down the time (for example 262.024 sec) - round up or down the time measurements: 0.001 to 0.499 is rounded down to 0.0, 0.500 to 0.999 is rounded up to 1.0) The calculation for the example would be: 3.522 -> 4.0 sec 262.024 -> 262.0 sec Total flight time: 262 – 4 = 258 sec = 4:18 min Please understand that race control will not discuss any time measurements, no exceptions here. Otherwise we would end up in endless discussions about the times that the pilots measured and what race control measured. We try to make this as transparent and fair as possible, but we are aware that there is room for small errors in the measurement process chosen.

Well, I put in the call signs that were provided in the emails when the track files were submitted. One guy didn't provide a name or call sign at all... Have to change it in 3 web pages then. Standby.... Editing mode started... ... Done !

Race Control has completed a thorough evaluation of the track files submitted for the Trans Crimean Race 2010 Qualification. Congratulations to all pilots ! Results are listet here: http://www.modern-air-combat.de/TCR2010/

Race Control has completed a thorough evaluation of the track files submitted for the Trans Crimean Race 2010 Qualification. Congratulations to all pilots ! Results are listet here: http://www.modern-air-combat.de/TCR2010/

MiG-29 MFD upgrade 1.3 Thank you for this great tutorial. You explained very well the reason why HUD and HDD range settings are different. For those who want to train themselves in estimating contact ranges, here is another tool that I developed in 2004: You can find it in the download section of the VJS 161: http://www.vjs-161.de/release4/downloads.php?op=filter&id=Patches&uid=Gast&ur=1&sid= Note: This kind of extra display on the HDD screen isn't realistic, there are no such extra lines in real russian aircraft.

Thanks for the hints, I will test it tomorrow. Because the overall participation was quite low, we try to accept all the track files that were submitted, so we will not loose any additional pilots for this event due to crappy track files. However, the rules provided clearly stated this (even in the ReadMe that came along with the mission file): "Be sure, that you have de-installed all Mods that could affect a proper replay of the track file submitted, especially Mods that manipulate the MEinit.xml." and "Incomplete or corrupt track files will not be considered by race control. Track files submitted after the dead line will not be considered by race control. Race control will replay your track file on a clean Lock-On / Flaming Cliffs installation. If your track file can not be replayed properly (e.g. your aircraft is shown in a wrong position and crashes close to the runway), you will drop out of the qualification." Beside this, I saw some differences in the track file headers, like the briefing text portion missing, which to me is a clear indication, that the track file was not generated using the original mission file (which contained the briefing part) or that the track file was manipulated in some way. I'm asking you: Why would somebody use a different mission file to create a track file for submission for the qualification ?? Race control repeatedly was asked to start the replay from the editor GUI, otherwise the track would not be replayed properly. Why are people making simple things so complicated ???

One track file could not be opened at all. It's listed as available track file amongst others, but when it is started, nothing happens. Some other files show an effect that we call 'super-zoom'. The track replay only shows some cockpit details like if you zoom in extremely, and the pilot position would be only a few inches away from the instruments... We tried to replay them both via the standard 'show' menu and also started from the editor, both with the same negative effect. We thought about a different / modified aspect ratios in the graphics.gfg and graphicsd.cfg files (wide screen settings such aus 16:10) but even on a wide screen system, the 'super-zoom' effect remains active. We thought about Track-IR as a possible source of problems, however, the track files showed 'super-zoom' on non-TIR and TIR systems. We are trying to run the tracks on various systems, XP/Vista, with TIR/without TIR, with LCD-wide screen and CRT monitors, with DX 10 and DX 9, with single core and dual core CPO, with NVidia and ATI cards and so on. We think, that probably some/ a mod that was installed or not properly de-installed or a combination of mods may have caused this effect.

Hi there, not yet, still some problems with a few tracks that can not be replayed properly. We try our best to make them run so we can score them. Takes some more days-

Check PM

Can't believe it. ED shifted Christmas to Nov 17th. Great news ! Thanks, ED !!

Maybe somebody of the Russian pilots could sent you a copy of the Russian voice ogg-files that are in the Lock On/sounds folder. There are sound files of Wingman 1, 2 and 3 so there you should find something that you can use for your movie. I recommend to post your request also over there in the Russion section of this forum.

Submission period for TCR qualification closed We closed the submission period at midnight, so far the participation is way lower than expected. :unsure: However, we will stick to the time schedule as planned. Evaluation of the track files submitted will soon begin. We expect to present the results at the end of next week. Total track files submitted: 47 (fortyseven)

We closed the submission period at midnight, so far the participation is way lower than expected. :unsure: However, we will stick to the time schedule as planned. Evaluation of the track files submitted will soon begin. We expect to present the results at the end of next week. Total track files submitted: 47 (fortyseven)