Butcher59

Then save your players.lua and restore it after patch! Or better, make a complete backup of the entire BlackShark Folder and restore step by step what do you need!

I saw the explanation of the modman in another posting after i wrote this. Was a bit too fast with my posting here ^^ .

Yeah, you have to do a bit handywork. Find the settings in the modman.ini for LockOn 2.0, add the equal settings for DCS in the regestrie and add the entries in the *.ini as well. Start modman and it works again. Bit short this explanation, but i hope it's understandable.

here, ModelLOD.txt.old.txt

But that's not the point. To hit a target with the AGM-88, you have to lock the target. If you fire the missile in the override mode, the missile will explode in front of you. And in whatever cockpit, exept the Su-25t, there is no chance to lock a radar side. It work's (for me) only with the Cockpit of the Su-25t and the Fantasmorgana Pod! But if you can work it out..., :thumbup:

If you can tell me where i have to look, i can try to help to find it out! :smilewink:

I have a little problem with the Tornado and the AGM-88. To deliver the AGM-88, you have to add the Fantasmorgana-Pod from the Su-25t into the Tornado_IDS.lua. But you can fire the Missile only if you have connected the Tornado with the Su-25t Cockpit. In all other HUD's, there is no cursor to move, only in the HUD of the Su-25t! Do someone know, how to add this into the HUD of other Cockpits???

Thanks for help, :thumbup:

It's a bit difficult, but you can make other aircraft like the KC-10A, F-16A, IL-78M and some other aircraft flyable. To make them selectable in the game is not the problem, but to make them flyable was a bit harder. First you have to edit the correlate *.lua file, for my example the F-16A.lua 1. X:\LockOn Flaming Cliffs 2\Scripts\Database\planes\F-16A.lua here you have to change the HumanCockpit = "no", with HumanCockpit = "yes" 2. edit the X:\LockOn Flaming Cliffs 2\Config\Input\Aircrafts\aircraftNames.lua and add following line: ['f-16a'] = _('F-16A'), 3. now you have to add a new folder within : X:\LockOn Flaming Cliffs 2\Config\Input\Aircrafts bsp. X:\LockOn Flaming Cliffs 2\Config\Input\Aircrafts\f-16a into the f-16a folder you copy anything you find for example in the f-15c folder wich is also within the Aircrafts folder!! 4. after this, you have to edit the CustomHuman.lua wich you can find here: X:\LockOn Flaming Cliffs 2\Scripts\Aircrafts\_Common. here you must add the following line: before: after: thats nearly all. But these settings have a little disadvantage, the cockpit is not where it should be, it is set in the mass of centre of the F-16A frame, but i found a solution! There is one more thing you have to do: into the folder x:\LockOn Flaming Cliffs 2\Config\View, you have to edit the server.lua file before: after: now you have the cockpit where it should be and it is 6dof capable!! Unfortunately i was not able to make all planes flyable, the KC-10A and the IL-78M are relative easy (i didn't test here the cockpit settings), the F-16A i had to play a bit with, but until now i was not able to make the IDS Tornado flyable. There are some more planes like the Tornado GR.3 and then there is the F-2 which should be the Tornado GR.1, so i don't know what i have to add or which variables to set. Problably some other can find it out. Maybe someone find other problems, so i have allways a ctd if i add the F-15C pit to the KC-10, The KC-10 was only flyable with the A-10A or the Su-33 pit. Don't know why, so do not ask At least i could not add more then one plane into the server.lua, if i add more, i have no hud anymore and the pit is in the centre of mass again! If someone can build an f-16 pit for FC-2.0 would be a great thing!

Tried as you wrote, but it will not work. :cry:

Thanks for answer! :thumbup:

I would like to know, it is possible to deactivate somewhere the messages if someone joyned the misssion or has someone/something shot down?

Then look a bit closer to the pictures and you will know! Looks not really interesting, but what do i know. :thumbup:

In the ME-Editor, only before you create a new mission. If you want to edit the coalition after the creation, it is only possible with an Texteditor like Notepad++. And that is not easy stuff!

With deactivated TrackIR, use RCTRL+RSHFT+(Keypad)2, 4, 6, 8, / and * to move your view backwards, forward, sideways, up and down and RSHFT+(Keypad)1,2,..., 9, / and * to move the head like you do with TrackIR. Gives good views!! Short reminder, there exist's a manual with a description of the key seqcuenses. Could be very usefull, .... sometimes! :music_whistling:

You do not really need to hold or to press the collective brake if you want to change your altitude. The only implemented funktion of the collective brake, is the input to the altitude-hold channel. If you change altitude in auto mode, press and hold "F" until you reach your altitude you wish and then just release "F". The altitude-hold channel will now hold this new height. Or, deactivate auto altitude-hold, change your height and activate auto altitude-hold again. That's all you need to do.

Take a look at this posting: http://www.virtual-jabog32.de/forum/viewtopic.php?f=36&t=9026 unfortunately it is in german, but maybe you can use it.

Das Handbuch ist in diesem Punkt wirklich irrefьhrend. KOM ist fьr den Lead, also dem Formationsfьhrer vorgesehen und man erkennt es an dem Doppelkreis im ABRIS. Die ID spielt hier nicht wirklich eine Rolle und dient auch mehr der Unterscheidung untereinander. Alle Nicht-Formationsfьhrer sollten die WINGM Einstellung wдhlen (ID 2 - 4) damit der Lead, wenn er denn separate Informationen senden will, diese auch zielgerichtet verschicken kann. Der REC-Modus ist ein passiver Modus, wie im Handbuch beschrieben, um eben so lange wie mцglich unentdeckt zu bleiben. Es kцnnen also nur Daten empfangen und nicht gesendet werden. Auch hier sollte jeder seine ID so wдhlen wie er in der Formation eingesetzt ist. Lead die 1, der Rest 2 - 4! Wobei der, der Informationen senden will, nicht im REC-Modus sein darf! Im Prinzip kann also jeder der nicht gerade im REC-Modus ist, Daten an jedem hin und her schicken, solange er sich auf der gleichen Frequenz (z.B. 127.500) befindet.

It works with the ingame comm menue, give a command to your AI Wingman and when he give an answere, the needle will move!

BS 1.0.1c

ok, i was wrong. I mixed it with Flaming Cliffs. Same here, it dosn't matter if there is wind or not, the ship's moving or standing still. The planes wan't land. They put their gear down and up down and up but never land. It's a matter for the bug section!

Do you have wind in the mission? Is the Carrier moving into the wind? I hade made a mission with wind and the carrier or the landing direction was not correct into the wind, so the F14 were not able to land on the deck. After i set the wind to 0m/s or turned the direction of the carrier so that the landing directin was exact into the wind, the planes where able to land. So this could be the problem.

yep, but... the NDB for Gelendzhik is not an NDB designed for a line up the ILS RWY, it is more an NDB to find Gelendzhik like an VOR or an VORTAC. So in the Beacons.lua you have to add some lines to make the NDB active. I don't know why they made so different programm code in the Beacon.lua (ask please the producer or programmer) but if you add some lines, you can make the Gelendzhik NDB aktive! This was the code in the Beacons.lua before changing: Airdrome[Gelendzhik]={} --http://dir.avia.ru/airports/59848211008598853.shtml Airdrome[Gelendzhik]["latitude"]=44.56370 Airdrome[Gelendzhik]["longitude"]=38.01186 Airdrome[Gelendzhik]["height"]=25 Airdrome[Gelendzhik]["runway"]={} Airdrome[Gelendzhik]["runway"]["04-22"]={} Airdrome[Gelendzhik]["runway"]["04-22"]["latitude"]=44.56935 Airdrome[Gelendzhik]["runway"]["04-22"]["longitude"]=38.01994 Airdrome[Gelendzhik]["runway"]["04-22"]["length"]=1800 Airdrome[Gelendzhik]["runway"]["04-22"]["side"]={} Airdrome[Gelendzhik]["runway"]["04-22"]["side"]["04"]={} Airdrome[Gelendzhik]["runway"]["04-22"]["side"]["22"]={} Airdrome[Gelendzhik]["airdrome"]={} Airdrome[Gelendzhik]["airdrome"][1]={} Airdrome[Gelendzhik]["airdrome"][1]["type"]=BEACON_TYPE_AIRPORT_HOMER Airdrome[Gelendzhik]["airdrome"][1]["subtype"]=FAR_HOMER Airdrome[Gelendzhik]["airdrome"][1]["callsign"]="ГН" Airdrome[Gelendzhik]["airdrome"][1]["frequency"]=1000000.0 Airdrome[Gelendzhik]["airdrome"][1]["position"] = "44'33'52N 38'00'55E 40" and this after i added some lines: Airdrome[Gelendzhik]={} --http://dir.avia.ru/airports/59848211008598853.shtml Airdrome[Gelendzhik]["latitude"]=44.56370 Airdrome[Gelendzhik]["longitude"]=38.01186 Airdrome[Gelendzhik]["height"]=25 Airdrome[Gelendzhik]["runway"]={} Airdrome[Gelendzhik]["runway"]["04-22"]={} Airdrome[Gelendzhik]["runway"]["04-22"]["latitude"]=44.56935 Airdrome[Gelendzhik]["runway"]["04-22"]["longitude"]=38.01994 Airdrome[Gelendzhik]["runway"]["04-22"]["length"]=1800 Airdrome[Gelendzhik]["runway"]["04-22"]["side"]={} Airdrome[Gelendzhik]["runway"]["04-22"]["side"]["04"]={} Airdrome[Gelendzhik]["runway"]["04-22"]["side"]["22"]={} Airdrome[Gelendzhik]["runway"]["04-22"]["side"]["22"][1]={} Airdrome[Gelendzhik]["runway"]["04-22"]["side"]["22"][1]["type"]=BEACON_TYPE_AIRPORT_HOMER_WITH_MARKER Airdrome[Gelendzhik]["runway"]["04-22"]["side"]["22"][1]["subtype"]=FAR_HOMER Airdrome[Gelendzhik]["runway"]["04-22"]["side"]["22"][1]["callsign"]="ГН" Airdrome[Gelendzhik]["runway"]["04-22"]["side"]["22"][1]["frequency"]=426000.0 Airdrome[Gelendzhik]["runway"]["04-22"]["side"]["22"][1]["position"]={} Airdrome[Gelendzhik]["runway"]["04-22"]["side"]["22"][1]["position"]["Z0"] = -20.0 Airdrome[Gelendzhik]["runway"]["04-22"]["side"]["22"][1]["position"]["S0"] = -1120 Airdrome[Gelendzhik]["airdrome"]={} Airdrome[Gelendzhik]["airdrome"][1]={} Airdrome[Gelendzhik]["airdrome"][1]["type"]=BEACON_TYPE_AIRPORT_HOMER Airdrome[Gelendzhik]["airdrome"][1]["subtype"]=FAR_HOMER Airdrome[Gelendzhik]["airdrome"][1]["callsign"]="ГН" Airdrome[Gelendzhik]["airdrome"][1]["frequency"]=426000.0 Airdrome[Gelendzhik]["airdrome"][1]["position"] = "44'33'52N 38'00'55E 40" now i changed in the ARK.lua channel 7 to Gelendzhik and.... voila, i had my correct entry into the picture on the right cockpit wall and if i switched to channel 7, the correct direction on the HSI was showed!!

How do you do it on an airfield or an farp? Switch Com to Ground Crew and then ask for fuel or amo. Nothing special.

Yes :thumbup: