Jump to content

JG14_Smil

Members
  • Posts

    2508
  • Joined

  • Last visited

Posts posted by JG14_Smil

  1. The airfields with these missing lines are:

     

    Kutaisi

    Sochi

    Gudauta

     

    This all falls into place now... these three airfields have NDB approaches but are not included on the default ARK.lua (and therefore the ARK-22 channel placard). When you guys edited and debugged the 1.2.4 files, you forgot about these three fields.

  2. Hello,

     

    One glorious night of sleep under my belt!

     

    I'll post a file today for offline use. I bet if a server was running it a MP connection would work too. If anyone has a beacons.lua from a version earlier than 1.2.3 or 1.2.4, please offer it here so I can get the missing lines for Sochi and Gudauta airfields that are missing the NDB's.

     

    The attached file will only fix the missing Kutaisi NDB approach in offline use. It is JGSME ready, but be sure to back up your original beacons.lua file!

     

    I am guessing this bug came about as these three airfields are not listed on the default ARK.lua file. ED has no beta testers that use NDB navigation, so these were overlooked while debugging.

     

    If it is not fixed in the next update, I'll not like E.D. anymore :P

  3. [TABLE] [Kutaisi] = { -- UGKO Kopitnari (Georgia)

    runway = {

    ["08-26"] = { --In LOBS map this airfield has 8 and 26 numbers drawed on runway's sides

    side = {

    ["08"] = {

    {

    type = BEACON_TYPE_ILS_FAR_HOMER,

    callsign = "КН",

    frequency = 845000.0,

    },

    ILS:channel('34Y', 'IKS')

    },

    ["26"] = {},

    }

    }

    },

    [/TABLE]

     

    Above edited code snippet has working ARK-22 while offline.

     

    [TABLE] [Kutaisi] = { -- UGKO Kopitnari (Georgia)

    runway = {

    ["08-26"] = { --In LOBS map this airfield has 8 and 26 numbers drawed on runway's sides

    side = {

    ["08"] = {

    ILS:channel('34Y', 'IKS', math.rad(3.0))

    },

    ["26"] = {},

    }

    }

    },[/TABLE]

     

    Above code snippet is from 1.2.4 and had no working ARK-22 Inner and or OUTER beacons (Kutaisi only has one beacon). There are several airfields that are affected like this in 1.2.4. If I can find them I am sure you can too. I note you edited the ILS lines and that is probably where the copy/paste errors came to be. I did not mean to include the obsolete ILS line in my example, but left it there to show my personal mistake when I edited.

     

    thank you.

  4. Hello,

     

     

    This is for the Ka-50 Blackshark in DCS World.

     

    Version 1.2.4. beacons.lua has some lines missing from Kutaisi, Sochi and a few other airfields. The lines are for the NDB beacons for the airfields and the ARK-22 no longer works at these fields because of it. I was able to easily fix it by replacing the lines and it works great offline.

     

    I cannot fly MP with the fix though, due to it clashing with the server. Please replace those missing lines in the beacons.lua in the next update. Do you need me to provide them to you?

  5. yes.

     

    Kutaisi is an easy fix, but my backed up version of beacons.lua does not contain the old info for other airfields like Sochi and others. Perhaps it is from one of the hotfix versions.

     

    Could someone please offer their beacons.lua from a BLackshark install? I could get the beacon info from that file to fix the rest of the bugged airfields. This is something that has to be pasted in as the lines contain Crylic fonts in the identifiers.

  6. Have confirmed my Kutaisi fix with a custom mission. It all still works. Editing the beacons.lua will bring us back to usable NDB navigation.

     

    I will also edit the beacons lua so that the NDB beacons will be listed by their frequency as shown on all the maps used by the Ka-50, as opposed to the Russian names that are listed. Will offer both versions.

  7. OK> I found a 1.2.3 version of beacons.lua, added the missing lines for the Kutaisi runway beacon to 1.2.4 beacons.lua and it worked. Placard shows Kutaisi and ARK-22 needle points to it.

     

    This is fixable on a local level for those that want to use ARK-22 navigation. I have 5 days off and will get to it. Will offer the file here when ready.

  8. One thing I note about 1.2.4 is my helo shows up exactly on taxi ways and runways, where there was some position error in 1.2.3. Not sure if this caused by the update or my clean install from 1.2.3. If work was done to fix that problem, it may have caused the ARK lua problem we see here (and maybe the GNSS CALC feature loss).

     

    I think our packaged ark.lua in miz files is still read, but there is a syntax error that makes the ARK-22 channel placard go blank on either the ARK.lua or beacons.lua files. We might be able to fix this on a local level by editing the affected files, but even with backup, the next update could make all the work a moot point.

     

    I hope I can find a 1.2.3 version and start comparing the two files.

  9. Headspace: so now we can't even do this because of realism? Please stop. Just let us enjoy our sim.

     

    Headspace #2: Please don't mind me.. I have had no sleep in three days. Salute for all you work with TARS and sound files!

     

    If we are counting on me we are in trouble. It is the smart guys that will help us if it can be done. I am just going through some trouble shooting items:

     

    I can edit C:\Eagle Dynamics\DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\ARK\ark.lua and it will show the changes. I can edit C:\Eagle Dynamics\DCS World\Bazar\Terrain\beacons.lua and it shows those changes. I tried entering Kutaisi and the lines went blank on the Ka-50 ARK-22 channel placard.

     

    I'll look into the miz file packaging after some fresh air.

  10. Lately, with my Nvidia hardware, the only thing that fixes tearing for me is to enable Vsync in SoftTH.

     

    TIR does not cause the tearing. It just shows it off more. You will see tearing when the initial zoom works if it is going to tear at all.

  11. Your resolution is 4720x1080. ratio is 4.37037037037

     

    Delete your softhconfig file.

     

    Start DCS and it will create a new one with proper numbers. Use the softh config tool and make sure keep aero on is checked (if using Helios) and "don't render unused space" is checked. Make sure the tool points to your proper file. If you need bezel management, do it with the softTH tool.

     

    You cannot line monitors up at the bottom, it has to be the top. That is where zero is.

×
×
  • Create New...