Jump to content

spirit_disease

Members
  • Posts

    67
  • Joined

  • Last visited

Personal Information

  • Location
    Nizhyn, Ukraine
  1. Совсем не так. Править частоты радиостанции индивидуального борта сможет только клиент который занял слот. В Неваде допустим, на Л-39 частоты радиостанции вообще не совпадают с частотами РП аэродромов, приходится править в редакторе, что не всегда удобно. Не вижу никаких сложностей - тот кому нужно поправит у себя индивидуально, на других слотах это никак не отразится. После уничтожения или выхода все сбросится в настройки заданные редактором миссий. По-моему идея нужная.
  2. Господа разработчики, возникла полезная "хотелка" - добавить в меню перевооружения возможность настройки частот предустановленных каналов радиостанций. Пожалуйста, обратите внимание, мысль то дельная, думаю сообщество поддержит. Править частоты в редакторе конечно можно, но не всегда удобно. Да и к реалу так ближе. Заранее спасибо.
  3. Мужики, не поверите - жена прочла мое объявление, говорит "костьми лягу, но продать не дам, ты шесть лет на это потратил". Весомый аргумент. Не ожидал даже. Закрывайте тему.
  4. Продам комплект Saitek x65f, железные одно-осевые педали на контроллере BRD-4000, track IR 5 без клипсы с кепкой и отражателями. Все железки закреплены на металлической разборной станине, РУС на жесткой площадке внизу почти как в реале. В общем - "подключил и полетел". Дефектов нет. Косметическое состояние имеет следы активного использования, но на работу не влияет. Покупателю в подарок очень крутой комплект ПО, плюс лицензионный FSX c VRS-F-18 и TackPack к нему же. Конструкция не маленькая поэтому только самовывоз из г. Нежин, Черниговская область, Украина. Продается все вместе и сразу. Цена - до 600 USD, будет разумная скидка на транспортировку. Обмен, продажу частями не предлагать. Продаю в связи с очень тяжелым жизненным положением, буквально отрываю от сердца. Шаг вынужденный, но необходимый. Надеюсь на понимание со стороны сообщества. Железо сослужит хорошему человеку долгую службу. Фото приложу в ближайшее время, сейчас возможности сфотографировать нет, нахожусь не в городе. Все вопросы в ЛС. Заинтересовавшемуся покупателю вышлю в лс номер телефона, чтоб обсудить детали. Честность и порядочность гарантирую.
  5. Beacons_V2.zip Hi there. There s new wersion of NTTR beacons mod. In this version 16 new RSBN navigational beacons added. List of the beacons and channels: :smartass:
  6. Thanks, It can be really helpful.
  7. David, in most cases, order of items has no matter. But elements nesting order is important. That will be correct: airdrome = { TACAN(31, 'X', 'TSK', {x = -281653.7, z = 647182.6}), { type = BEACON_TYPE_RSBN, callsign = "SI", frequency = 831000000.0,-- channel 31 channel = 31, position = coordinates("42'14'25N 042'02'48E"), }, } First. comma after ')' and '}' is very important, you must separate every pair of opening and closing brackets, like that: ( --airdrome 1 { -- some parms here dont foreget commas at the each parameter's end param1 = 'value', param2 = 'value2', }, { -- other params here, etc } ), ( --airdrome 2 --place whole params block and '{}' here ), Second, you must insert whole block of params insert inside brackets like shown up. Third, commas after ecach param. But some details may be changed in context of realisation, - I am mean that sometimes '()' or '{}' or even '[]' brackets must be used, last pair of brackets may no need comma after it. So, you must always carefully look at existing ED's code before attempting to modify or add something in it - and write code absolutelly similar with it.
  8. Did you palce RSBN stations exactly opposite to middle-point of each runway?
  9. Thank you, David. As soon as I am can find a free time, I will continue this work in Nevada first, due to next changes in Caucasus map in 2.5, I am dotn see a reason to do something there until 2.5 will be released, because there's no guarantee that beacons will stays unchanged by ED. Main principle of good coding is - DRY (Don't Repeat Yourself) Cheers)
  10. You must add heading and elevation above sea level for PRMG localiser and glideslope, you can got elevation from ME and heading from ILS beacon if it exist on runway. Also, for PRMG localiser offset from runvay end needed too. Look at my realisation - for example, Groom Lake AFB : chartOffsetX = 4269.000000; --- offset position = { -286660.593750, 1357.831973, -87720.343750 }; -- elevation is 2nd param (1357.831973)
  11. It seems there are "frequency range" higer than 800 mhz that must be in corellation with the channel number. So if 8XX is frequency that used, than XX will be channel number. Download my mod, open it with Notepad++ and compare with original file, or witn Caucasus map Beacons.lua file. If you will closely look in diferences and read the comments that started from '--' you will understand the method used. Note that ED used on Caucaus map two different types of beacons realisation, its has different code structure, in other side, Nevada map use only second, new type. Again, read the comments in file carefully. If you not familiar with russian laguage and Google translator give poor result, PM me and I send you translation to English as soon as I have possibility to do that. Cheers )
  12. BeaconsMod.zip Hi David, this is looks strange, here's new link in .zip archive.
  13. Thanks, David ) I am absolutely assured that in DCS community many users also trying to find the solution. For example, I am had exactly the same idea about mobile navigaton beacons, but can not find any practial ways to its realisation. Any user, who had even html editing skills, even on minimal level, CAN add static beacons on any map, include Caucasus too. My mod main priciple is not in any "hacks" or adding any new algoritms to existing ED code. I am just set up parameters - coordinates, headings, frequencies, etc , using standart ED realisation. Main trouble in that fact, that we can not get coordinates in required format from mission editor, and every beacon that you need to add must be set up manually on map, that requires many (sometines 30-50 attempts) manual "geoposition" corrections in code for each beacon, and it is so sloooow ( I am absolutely sure that in our community are users who can find more effective method of setting up geographic positions of beacons. The more easy way MUST be present, even if I am can not see it, but someone will. I am just want show to community a possibility to do that. Together we CAN make our DCS World better. With best wishes, Max.
  14. This mod CAN NOT work with Mig-21. Leatherneck Simulations used completely different realisation scheme, because there's no RSBN in DCS World at moment of Mig-21 release. They used IMHO not the best solution, but they simply had no other choices. Implementation STATIC RSBN/PRMG for Mig-21 is very similar to my mod creating priciple, but its must be done in Mig-21 module code. If you open two files Mods\aircraft\MIG-21bis\Cockpit\Systems\R_NAV_data_Nevada.lua and Mods\aircraft\MIG-21bis\Cockpit\Systems\R_NAV_data_Caucasus.lua with any text editor like Notepad, Notepad++, etc., you will see the princpile of its realisation. Of course, if you have any minimal coding skills. But implementation of MOBILE RSBN/PRMG or other similar systems, is a completely different task, and I think only ED or big 3rd-party developers team can do that pretty cool thing. EDIT: I think that there's no way to use Mig-21 reciever in L-39 and vice versa. There is fundamental, complete difference, not only in code, but also in systems "architecture" design. In other words, the main difference between LN and ED RSBN/PRMG realisation is in that fact, that ED "virtually transmited" signals in DCS World, and any aircraft that have that systems realised like in L-39 will "virtually recieve" this data. LN creates "simuation in simulation" - BOTH transmitter and reciever parameters is hardcoded in Mig-21 module. That means if ED creates any map that contains theese navigational systems, any aircraft that uses ED's method automaticaly got working navigation without any changes in its code. In other side LN will need to code changes for ANY module and ANY map where this navigational equipment present and must work. I hope that guys from LN understand all limitations of that's approach too, and will re-worked this code in future. Excuse my poor English, hope that you will understand what I am mean. Cheers ) UPD: In topic context, this also means that even if anyone create mobile RSBN, it will work with L-39, but will not work with Mig-21 until LN not change own RSBN code architecture to ED's version.
  15. Выкладываю личный мод для внедрения АРК и РСБН/ПРМГ в Неваде для Groom Lake AFB, Creech AFB и Toponah AFB, пробуйте кто желает. Приношу извинения за отсутствие перевода, по сути и так все ясно. Меняйте файл с заменой в Mods/terrains/Nevada - не забывайте про резервную копию оригинала. [ATTACH]158578[/ATTACH] Here is my own attempt to implement RSBN/PRMG and ADF on Groom Lake, Creech and Toponah airports. This mod is EARLY WIP, and may need of more precision parameters setup, but IMHO it works correctly. Maybe, some coding skilled entusiasts will take this idea and complete this work, because unfortunately I have lack of time to do this for all airports in map. List of frequencies and channels: ADF: Groom Lake: ADF on 700 and 710 Khz (near and far homer single direction) Creech: ADF on 760,770,780,790 Khz (near and far homer for each runway, both directions) Toponah: ADF on 720,730,740,750 Khz (near and far homer, both directions). RSBN/PRMG: Groom Lake AFB: RSBN:channel 20 (navigation) PRMG:channel 22 (landing system, single direction) Creech AFB: RSBN :channel 28 (navigation) PRMG:channel 30, 32 (landing system, for each runway, both directions) Toponah AFB: RSBN:channel 24 (navigation) PRMG:channel 26 (landing system, both directions) INSTALLATION: simply put in Mods/terrains/Nevada and replace the existing file. IMPORTANT !!! You should use this mod on your own risk, don't forget to make backup of original file. This mod will not work with Mig-21, LN has different realisation of theese systems. KNOWN ISSUES - ADF fequencies and RSBN/PRMG channel numbers will NOT shown in F10 table of frequencies, but in Mission Editor you should see all beacons on map. For correct use of PRMG in L-39, don't forget to set up barometric pressure on right console UPD: Поправил ссылку на вложение
×
×
  • Create New...