Jump to content

ajax

Members
  • Posts

    491
  • Joined

  • Last visited

  • Days Won

    1

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. For the Ka-50 in the HUD-only view I used to see the ABRIS inset into the lower right of the Shkval on my second monitor. Since DCS 2.5.6 the ABRIS no longer shows up. Any clues? This is my monitor setup file: _ = function(p) return p; end; name = _('my_monitorsetup'); Description = 'Shkval on the left monitor, camera on the right'; Viewports = { Center = { x = 0; y = 0; width = 1680; height = 1050; viewDx = 0; viewDy = 0; aspect = 16/10; } } LEFT_MFCD = { x = 1680; y = 0; width = 1680; height = 1050; viewDx = 0; viewDy = 0; --aspect = 16/10; } Gui = { x = 0; y = 0; width = 1680; height = 1050; } UIMainView = Gui --ABRIS = --{ -- x = 2688; -- y = 147; -- width = 568; -- height = 756; --} --UIMainView = Viewports.CenterI tried uncommenting the ABRIS section but that had no effect.
  2. The problem is that in order to allow Combined Arms players the ability to jump into various ground units you have to make them visible on the map. If units are set to visible then air-defense units (not all units) will show up on the Ka-50's ABRIS. Enabling fog-of-war does not prevent this. Also, it seems that the indicator on ABRIS is only linked to the actual air-defense unit in the group. If that unit is destroyed, the next time you start up ABRIS it will no longer appear even if other units in the group are alive.
  3. The key to getting the laser repaired without having any other damage is to simply use the engine fire extinguisher before asking for repair. (I didn't come up with that -- I read it here on the forum some time ago -- don't remember who came up with that solution, but thanks!)
  4. Version for DCS 2.5.5 is available at the top post. Everything works except for the "FixBorts" button. I disabled that function because, frankly, there are now too many DCS aircraft to keep up with.
  5. Okay. I've got it working for 2.5. There were a lot of changes to various ME components that I had to figure out. I still need to do a little more testing, but expect an update in a week or so.
  6. PM sent, crazyeddie. Yes, I'll try to make it work for 2.5
  7. You're welcome. Glad I could help.
  8. Sure. The time values are in seconds, so change the first value from 102.150000 to 112.150000, the second from 103.616000 to 113.616000, the third from 103.706000 to 113.706000, and the last one from 109.650000 to 119.650000.
  9. This bug was introduced quite a number of updates ago. The problem is that not enough time was allowed for the left engine to completely spool up in the startup macro. You can edit the {DCS}\mods\aircraft\ka-50\cockpit\scripts\macro_sequencies.lua file to fix it. Open the file and the look for the following section around line 243 (in my file). [font=Courier New]--[[ Переключатель двигателей четырехпозиционный --]] {time = [color=Red]102.150000[/color],device = 4,action = 3008,value = 0.200000}, --[[ Запуск выбранного двигателя --]] {time = [color=Red]103.616000[/color],device = 4,action = 3005,value = 1.000000}, {time = [color=Red]103.706000[/color],device = 4,action = 3005,value = 0.000000}, --[[ Стоп-кран правого двигателя --]] {time = [color=Red]109.650000[/color],device = 4,action = 3010,value = 1.000000}, {time = 120.8,message = _("STARTING AIRCRAFT - 1 MIN REMAINING"),message_timeout = 55.0}, [/font]If you add 10 seconds to each of the values in red it should fix the problem. After you get it working you can try to decrease the values gradually to minimize the startup time. Edit: I take that last part back -- because there are other steps afterwards and you aren't adding any time to them, the total startup time is unaffected.
  10. I haven't run across that partcular issue; but you're right, that would explain the behavior in the OP.
  11. I think an old bug, once fixed, has resurfaced. The bug involved losing contact info on the abris if using the default frequency of 124.000. Try changing the frequency.
  12. @StrongHarm: Complete agreement here. @microvax: Unfortunately, I don't think there's any way to "update" the ABRIS except by respawning.
  13. I have to disagree with some of the earlier answers: The units displayed on the ABRIS do indeed change as the mission progresses. The changes are only seen if you respawn, as the original poster said, and if they are set to visible. It seems that only unit #1 of any group is seen. If that unit is destroyed and the player respawns, that unit/group will no longer show up on the ABRIS.
  14. That should work for a Red FARP. For a Blue FARP, regardless of the country, you will need the blue units FlankerOne listed in post #2, i.e. M-818 and HEMMT.
×
×
  • Create New...