Jump to content

Delta99

Members
  • Posts

    458
  • Joined

  • Last visited

Everything posted by Delta99

  1. Disagree with the F15. I always adjust but its a bit different than the A10. In the A10, the default centre position is like a foot forward from the seat. The F15 at least you are properly positioned in the seat.
  2. Interesting. So ED decided to have the default position leaning forward. That is why the chair seems so far back. Be nice if there was an option to leave the default position like it would be in real life and then we would all know that you need to lean forward to see the HUD properly. Strange that it would be like this in real life though!!!
  3. So what does it let you do? I assume it allows you to take lets say a live recorded session (the audio portion) and match it up to tacview so while playing back you can hear your audio as it was during live recording? This would also make it SO much easier to match up video segments when I edit my videos. Currently it is pretty hard to match up recordings I make of Tacview with my live recordings. Seems like it would be easy but if you are off by a few frames things don't look right. I've got a lot better recently at editing these as I finally had to learn how to move a video file frame by frame with keyboard commands. So, I can slide it left and right to match it up with live video.
  4. This is what you want: redBorderZone = ZONE_POLYGON:New("redborder", GROUP:FindByName( "redborder" )) redgcicap:SetBorderZone(redBorderZone) redgcicap:SetSquadronCap( "101", redBorderZone, 4000, 10000, 700, 900, 800, 1100 )
  5. What update was this added in? I’ve searched back and found nothing. Where can I find info on this feature?
  6. I like this idea. I’m inclined to try and develop some missions but poor at coming up with story ideas and background etc.
  7. I never use the prepare mission because I believe it saves any changes you may make while testing ("preparing the mission"). Like any cockpit changes, radio changes etc. This is probably why your A10's would not reload their DSMS. At least that is what I understand Prepare Mission doing. So, no need to use that if you are just testing a mission while designing it. Just use fly mission.
  8. Same, always have troubles in MP with this type of stuff. Works fine in SP though and possibly the host that logs in as SUNTSAG says.
  9. Purely by luck and some of these techniques and probably some others.
  10. There is this too which you should definitely read in detail: http://flightcontrol-master.github.io/MOOSE/Documentation/Event.html
  11. Try removing the local on the SPAWN object. You need a global object there.
  12. I think I asked for both versions too when it was changed to strip all comments. I knew there would be a lot of requests for the original with comments.
  13. So far so good with the stutters as far as I can tell with this latest hotfix. Thanks for looking into that and fixing @ED
  14. Great, I'm sure you'll have a lot of fun with this. My Valley Escort and Patrol missions both use this if you wanted to take a look. Links in my signature.
  15. If I am not mistaken, AI_PATROL_ZONE sets engagement to off for some reason. I would rather that be left to the mission designer. You might be able to set the engagement back on (I forget what the method is but try looking in CONTROLLABLE. However, may not work as AI_PATROL_ZONE might reset it whenever it sets a new route. What you really want to use is AI_CAP_ZONE most likely. Works almost exactly the same as AI_PATROL_ZONE but you also setup an engagement zone. Take a look at CAP-011 demo mission. All this was changed maybe 6-8 months ago when AI_CAP_ZONE was born.
  16. FC, what exactly was the fix? I looked at the code but didn't really understand what the differences were. For me AI_CAP has worked for a long while without issues especially with regarding to engagement. At least as far as I can tell.
  17. Do you mean they don't instantly respawn while you (human group leader) are still flying? Then no, they probably don't respawn until you die and restart in the same slot. All of this will be standard DCS behaviour that Moose cannot help with. However, you might be able to kind of do what you want in the form of using Escort type tasks. But then you won't have a real wingman (ie. you won't be the group leader and have menu actions to command them) but rather just a unit that will fly escort with you. Then you can respawn that unit as you like with Moose. All depends what you are really trying to accomplish and how much scripting you want to do.
  18. If the wingman is dead then yes they will respawn with you. If not they just act as your wingman after you spawn back in unless you spawn back into a different slot.
  19. What is the error in the DCS.log file? Spawns could take a second or two before they are available so you can try moving the spawn of the plane before you define the zones. That might give it enough time to the be able to set controllable on it. If this is in fact the issue.
  20. This is very unlikely to work and will most likely be a DCS limitation.
  21. You might want to post the code your using to do this
  22. Need an explanation. Seems fine in VR to me.
  23. Thanks for looking into this Grimes
  24. Look at some of the threads where people were on the fence. For those that got the Rift they were blown away and couldn't believe they waited this long. You will NOT be disappointed.
×
×
  • Create New...