SwingKid

Welcome aboard! Ah, to be 18... Wanna trade? :) -SK

The terrain information has already been hacked: http://forum.lockon.ru/showthread.php?t=7097&highlight=merzifon The problem is that it's half a gigabyte, you need to write your own computer programs to manipulate that amount of data. -SK

http://3dgraf.ru/lockon/pilot1.html -SK

Ooh, there! I knew that. :) (Sorry, too much recent text-editing made me think I could be funny...) -SK

Where? :confused: -SK

Try whispering that in the ear of an F-22 guy... :) -SK

That should be part of the "NITKA" pilot training system, that includes arrestor cables and a ski-jump ramp for simulating Kuznetsov carrier ops. -SK

Jet engines usually radiate much more heat than light. TV seekers are also generally heavier and more expensive, only used when an imaging seeker is absolutely required (usually to pick targets out of ground clutter). There are cases of TV-guided Mavericks hitting slow aircraft in flight, but that's not a cost-effective way to do the job. Note that even IR A2G weapons all need imaging (IIR) seekers to see targets against ground clutter, whereas A2A can usually get away with a single non-imaging IR element. -SK

Where could one reach Pat01 to ask about programming tips? -SK

I usually rename it to a ".wri" file, and then edit it with WordPad. -SK

Which part you don't understand? -SK

Alfa is correct, adding new objects to the .scn files is presently beyond my skills. Creating a tree perimeter out of existing map objects would be possible, but very difficult, requiring me to do over almost the whole mod from the start. Maybe someday when my other projects are finished. -SK

No plans for this right now, since it would require removing an airbase that does exist. There are many small towns in the former Soviet Union named "Razdolnoye". Maybe this is a real airbase from one of those other locations, outside Crimea, and the original Flanker 2.0 map designer was confused. -SK

Right now work is focusing on the Ka-50 and "v1.2", but all kinds of avionics ideas are actively collected, discussed and considered in a "planning stage". Which ones actually get implemented, and when, will probably depend on how well they fit into the grand scheme of things. ED has recently shown ever more willingness to limit the scope of their products. -SK

It did not say, in the "Cassegrain.rar" document that Vadifon sent to you, that MiG-23/25 radar uses monopulse tracking? From where, "con-scan"? :confused: -SK

Ah ok you were talking about a normal intercept. I thought we were talking about the radar missile seeker doing some kind of scanning without a fighter tracked target. I'm a little fuzzy on the precise mechanics of the often-talked-about "mad-dog"/"bull-dog"/"pit-bull" (?) mode. -SK

Where can we read more about these? Never heard of them... -SK

When I was a kid, I liked to play on the swings. I'd pretend I was flying an airplane. -SK

Is this not already included in Lock On, since Flanker 2.0? I fly over it often! :confused: -SK

Wow, someone who is interested in keyboard controls, AND writes in both English and Russian?! :) Welcome to our discussion! I also started my interest in this topic because I was not satisfied with the implementation of a few keyboard controls (e.g. Alt-KPDel for missile padlock), and also with the proposed solutions "get a HOTAS" or "re-program the commands yourself". The more that I study the problem, however, the more I realize that it's a very complex simulator, and an efficient layout cannot be accomplished by simply changing one or two commands. In addition to the question of what should happen when Shift or Alt is released - I think we should also take advantage of Caps, Num and Scroll Lock as their natural mode-toggling "Lock" functions imply (Lock On presently uses them as ordinary keys like any other, and ignores whether the lamp is active or dark on the user's keyboard). And there are some functions that are less necessary, and could be moved to on-screen menus, to make space on the keyboard for more often- or urgently-used controls. At this time I am most concerned about the Keypad "view" controls. For example, in the F1 view, the zoom keys KP* and KP/ will change the angular field of view, but not the camera position. In the F2 view, the zoom keys KP* and KP/ chane the camera's position, and Ctrl-KP* and Ctrl-KP/ change the angular field of view. The use of KP0 as a sort of "Shift" key for snap views is also very strange. And the use of "Win" keys in general has given problems to people who don't have such keys on the keyboard, or cannot map them to the HOTAS. I studied these view controls and am now convinced that it will be the most difficult part of the user interface to redesign - the efficient switching between snap views, panning views, stepping views, view saving and adjustment controls, all the different kinds of padlocks, 6-DOF TrackIr compatibility, future front seat/back seat views and everything else threatens to consume the entire user interface with a million commands that have nothing to do with controlling the aircraft. Until this part of the user interface can be re-organized with a smaller "footprint", it will always hang as a dark cloud over all other keyboard controls - important flying controls must scavenge obscure real estate like "RWin+Insert" because there is not other place for them. So I think that all keyboard control solutions should be carefully planned and considered together, at the same time, with consideration of all of them according to prioritization, and not individually. And as Valery suggested, the operation of view controls is a very large and serious part of the consideration. Probably, such a project of user control revision will require such time and work that it should be planned only for a distant future product. I worked some time on a new plan for view controls, I'll try to post it soon for discussion. Thanks for interest! -SK

hip = pirate? -SK

What does the tag say? -SK

-SK

piece of hardware = big man with stick -SK

Are you sure it was a moderator? I thought almost everybody could influence rep points. -SK