logo12307 Posted September 2, 2011 Posted September 2, 2011 If i set a Datalink NAV point and saved it to the ABRIS, how cam i say the wingman to fly to it and stay there??? I tried much ways but none of them worked. please help me quickly. Logo12307
lvl4f Posted September 2, 2011 Posted September 2, 2011 (edited) See this videos, (Producer Notes), I hope that this help you. Edited September 2, 2011 by lvl4f
logo12307 Posted September 2, 2011 Author Posted September 2, 2011 Thx but i have known these vidios before. Another question after patch 1.02 you cant set INU Fixpionts in the mission editor. do you have this problen too or is it only by me? Logo12307
lvl4f Posted September 2, 2011 Posted September 2, 2011 Pardon, but I do not use the missions editor, I have always used already made missions. Perhaps another person could solve your doubt.
ZoomBoy27 Posted September 3, 2011 Posted September 3, 2011 Thx but i have known these vidios before. Another question after patch 1.02 you cant set INU Fixpionts in the mission editor. do you have this problen too or is it only by me? It is a bug - not in the game but the Mission Editor being able to add the Point There is a work-around Load a functioning stock mission with a INU point in it already - and then File... Save As... There's another method - but it requires Unzipping the .miz file and inserting the proper code - :book: :cry: :renske: :surrender: ZoomBoy My Flight Sims Page - Link to My Blog - Sims and Things - DCS Stuff++ - Up-to-Speed Guides to the old Lockon A10A and Su-25T - Some missions [needs update]
Yurgon Posted September 6, 2011 Posted September 6, 2011 Thx but i have known these vidios before. Another question after patch 1.02 you cant set INU Fixpionts in the mission editor. do you have this problen too or is it only by me? If you're not afraid to edit a config file, you can easily fix the mission editor: http://forums.eagle.ru/showpost.php?p=1056893&postcount=11 (The file to be edited is BlackShark\modules\me_map_window.lua). This fix works with 1.0.2. It's quite possible that ED is going to fix this issue with the upcoming compatibility patch, though.
Recommended Posts