Jump to content

rmk80

Members
  • Posts

    131
  • Joined

  • Last visited

3 Followers

About rmk80

  • Birthday 07/17/1980

Personal Information

  • Flight Simulators
    X-Plane 11
    Digital Combat Simulator
    MSFS2020
  • Location
    Netherlands
  • Interests
    Simulators, VR

Recent Profile Visitors

3687 profile views
  1. Hey, I really appreciate some of you are still enjoying and playing this mission and the fact that is still running on current versions. I like your idea of adding static targets and I do think it is possible. First thing to check is if all required Moose functions are available for static objects as well (not sure). Apart from adding the statics in the mission editor, it requires adding a new category to the script. This will take some edits. Maybe I can have a look when I’m back from vacation
  2. Wow great find! Im gonna have to dive into Helios to see if I can replicate your solution
  3. Well, after some intense flying since the OB with the fix I haven’t had any freezes anymore! Very happy that this issue that had been bugging me since April has been fixed. A true Christmas present
  4. Ah great, thx for confirming! I will check and see if I can reproduce the freezing
  5. Or you could use Voiceattack, works perfectly for VR
  6. Hi, if I hide the cockpit with Alt + F1 the buttons on my UFC no longer function and it is also no longer synchronized. If I unhide the cockpit everything is back to normal. Is this intended/normal behaviour? Is there a work around? The DDI’s do keep working without the cockpit visible.
  7. rmk80

    MIP Restock

    I received the tracking link just today. Now let’s see what I have to pay to customs! Probably another 21%
  8. rmk80

    MIP Restock

    Same for me. Has not been shipped yet
  9. Yes, I can fly any other module without freezes as long as there are no F-14s in the missions. if they are present, the game freezes no matter the module I’m flying. Disabling the F14 module did not change this behaviour.
  10. Is there already any progress/news on this issue?
  11. This might be caused because a FARP is considered as a group, but with "dead" units/objects in it (just guessing). Somehow the original counting of total units (when saving) has a different result then when you request a status report. You could try to add two lines. First: (see line that has THENAMEOFYOURFARP) --SAVE TOTAL UNIT COUNT totalRedUnitCount = 0 totalBlueUnitCount = 0 local AllGroups = SET_GROUP:New():FilterCategories("ground"):FilterActive(true):FilterOnce() AllGroups:RemoveGroupsByName("THENAMEOFYOURFARP") SCHEDULER:New( nil, function() AllGroups:ForEachGroupAlive(function (GROUP) if GROUP:GetCoalition() == 1 then totalRedUnitCount = totalRedUnitCount + getAliveUnitsGrp(GROUP) end if GROUP:GetCoalition() == 2 then totalBlueUnitCount = totalBlueUnitCount + getAliveUnitsGrp(GROUP) end end) Second: (see line that has THENAMEOFYOURFARP) BLUE_TARGET_SET = SET_GROUP:New() BLUE_TARGET_SET = RemoveGroupsByName("THENAMEOFYOURFARP") Not sure if this will work though
  12. I got the same error just now. Never seen it before
  13. Ok, that didn't take too long. Just had a freeze when switching views.
×
×
  • Create New...