golfsierra2

Try the search function of this forum http://forums.eagle.ru/showthread.php?t=40711 http://forums.eagle.ru/showthread.php?t=38770 http://forums.eagle.ru/showthread.php?t=37067 you might find even more threads and hints

FC 2 ? Haven't managed to land a western type on a road yet. It worked out in FC 1.12 ....

Depends on the aircraft that you choose. MiG-29A and -S, Su-27, Su-25 and -25T can land on and take off from any road on the map. All western aircraft types will crash trying this.

Mmmmh. Da gehen die Meinungen aber weit auseinander. Viele sind doch daran interessiert, eine möglichst realitätsnahe Simulation zu bekommen, und da ist es eben normal, das bis auf die Menüs und den Editor / das Handbuch entweder alles in russischer oder englischer Sprache ist.

Ich schließe mich Deiner Meinung nicht unbedingt an. Im Grunde betrifft die Lokalisierung - Soundfiles (AWACS/Betty/Nadya/Tower) - Cockpitbeschriftungen (Buttons, Anzeigen) - Menüs - Handbuch Alles bis auf das ausführliche Handbuch läßt sich also grundsätzlich auch als Patch realisieren.

Well, dealing with his wife is a lifetime experience and usually very challenging for every married man. There is nothing that you could really learn from others, every wife is different. I think it's best that you find your own way with dealing with your wife.... :music_whistling:

:no_sad:

Haven't read a word about ranges yet. The MiG-29 radar is much less effective than the Su-27 or F-15C radar in terms of detection ranges. You'll have to be much closer to another aircraft to see it on the radar. Within 70 km of range it will show you targets, but a F-15C or Su-27 then will have tracked you already and maybe even fired a weapon in launch override.

Have you tried to neutralize the trim ? CTRL + T IIRC

Correct. http://www.navysecurity.navy.mil/documents/information/intro-natosecuritybrief.pdf

For all who want to see the HOTAS of the Typhoon in Detail (e.g. for modeling a stick and throttle like that for a pit), here are some shots of a Typhoon HOTAS taken at the manufacturers stand at the ILA Berlin.

Taken 9 June

I know that the EOS of the MiG-29 and Su-27 can pick up other aircraft from many kilometers away, and even better from a chase position if the other ignites his afterburners. But, even within very close ranges, the EOS will not show any flares or will stop tracking by flares fired. Does the EOS simply ignore flares ?

I'd like to address this proposal to the lua experts here in this forum (I know, there are some guys familiar with lua here): For the time beeing, the Integrity Check (IC) only compares selected files / folder retrieved from the client with those available at the server side. If both match, nothing happens. If both are different (likely because the client side was modified), the connection will be interupted and the client can not join the server. The workaround found to make this IC acceptable for clients using modified files (usually because of system performance or graphics issues) is, that some units operating servers provide a ModMan compatible Mod which has to be installed before the client can join. Those Mods contain the original game files that have to be installed on the client side in order to pass the IC. Now: The IC routine is called in the main.lua: local scripts_dir = "./Scripts/net/" local config_file= "./Config/network.cfg" package.path = scripts_dir..'?.lua;'..package.path server = require('server') client = require('client') -- load config file local function append(dest, src) local k,v local present = {} for k,v in ipairs(dest) do present[v] = true end for k,v in ipairs(src) do if not present[v] then table.append(dest, v) end end end local function merge(dest, src) local k,v for k,v in pairs(src) do local d = dest[k] if k == "integrity_check" then append(d, v) elseif type(v)=="table" and type(d)=="table" and v[1] == nil then merge(d, v) else dest[k] = v end end end local function load_env(filename, env) local file, err = loadfile(filename) local res = false if file then if env then setfenv(file, env) end res, err = pcall(file) end local msg if res then msg = "OK" else msg = err end log("loading "..filename.." : "..msg) return res, err end My sugesstion is to modify the server side main.lua. It should not only compare one set of client files with the server files, but also give the client a second (third, fourth ?) chance to pass the IC. This could be achieved by adding an "or" case to the IC routine, so that it would look in the standard directories of the server installation and compare those files with the client side, but then in another (and another and so on..) step also compares one ore more additional file sets with the client side. Those extra files should be stored under a dedicated path in a different directory on the server side. Those files will never be called by the server's FC2.0 installation, as it only operates with it's own files, however, one could built a 'library' of known and harmless modified files, which also would be allowed to pass the IC. I'm a lua noob, but this is my first Idea as how the main.lua portion could look like: local scripts_dir = "./Scripts/net/,Scripts2/net/," local config_file= "./Config/network.cfg,./Config2/network.cfg " package.path = scripts_dir..'?.lua;'..package.path server = require('server') client = require('client') -- load config file local function append(dest,src1,src2) local k,v local present = {} for k,v in ipairs(dest) do present[v] = true end for k,v in ipairs(src1) do if not present[v] then for k,v in ipairs(src2) do if not present[v] then table.append(dest, v) end end end local function merge(dest,src) local k,v for k,v in pairs(src1) do local d = dest[k] if k == "integrity_check" then for k,v in pairs(src2) do local d = dest[k] append(d, v) elseif type(v)=="table" and type(d)=="table" and v[1] == nil then merge(d, v) else dest[k] = v end end end local function load_env(filename, env) local file, err = loadfile(filename) local res = false if file then if env then setfenv(file, env) end res, err = pcall(file) end local msg if res then msg = "OK" else msg = err end log("loading "..filename.." : "..msg) return res, err end

It is this way since Lock-On 1.0.

Sounds like a plan to me ... FC 2.0 will install in a separate directory by itself, but of course you can guide it to where you want to have it installed.

Well, thank you all anyway. She made it, started with her first casting show in February this year. From zero to Euro winner in four months ! Amazing !

C'mon guys, make Lena the winner ! Vote for her !!

Yes, you can: http://forums.eagle.ru/showpost.php?p=763561&postcount=4 Another solution http://forums.eagle.ru/showpost.php?p=894154&postcount=8

Maybe far-fetched, but have you tried to assign a different key for starting the game ? I was just thinking about a problem with your keyboard driver/setup, that may need one of the DLLs replaced by your new video card driver. The Pause/Break button or to be more precise the command is of a different nature than other keyboard commands. Just give it a try, you won't ruin anything.

You make me stolz on you ! Danke für die Info !

Thank you very much, that did the job !

I can't figure out why FC2.0 won't accept my TIR4 anymore after I applied the latest patch. The options menu should look like this but it looks like this The column for TIR doesn't show any options, can't select a function there. I read this thread http://forums.eagle.ru/showthread.php?t=51398&highlight=TrackIR&page=2 and tinkered with the profiles in TrackIR. I reinstalled both Lock-On 1.0 and FC 2.0 and patched it with 1.2.1, and even reinstalled my TIR4 software. I tried it with the default Black Shark profile and with a custom made, no luck yet. I'm running TIR Software 4.1.037 B (which worked fine with FC2.0 before the patch 1.2.1 !) Any suggestions ?

The manouvers are not described with the G-loads involved. You can fly an Immelmann at 420 kts with 2.5 g and you can fly it with 5 g. It's still the same manouver, but in the latter case, you bleed much more airspeed, loosing energy. Try the same manouvers with less stick movement, e.g. don't pull so hard.

Usually, wheel brakes are apllied symetrically by pushing both pedals at the same time. Steering is achieved by pushing only one pedal, this affects the nose wheel.