Swany

I only ever use cold starts on the Stennis - Start from the ramp - However, I've only ever been able to place 5 (4 in one, 1 in another) on the Stennis UNTIL this latest Bug release - Now it's 4 and 4 only, regardless of where you try and put them

ForEachGroupCompletelyInZone, if I'm following right, wont work. He wants it if 1 helo from the group enters. They would have to all be in the zone for this to trigger. Might want to look for ForEachGroupPartlyInZone? Can double tap the docs :) https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Core.Set.html##(SET_GROUP).ForEachGroupPartlyInZone Only issue I see from that is then, as each one enters the zone, it'll trigger

First, please see attached logs - Mission went ok, we landed, and while in the process of shutting down my 18, game locked up for me (in MP) but not for others. Again, with the ACCESS_VIOLATION event I use glogg constantly - When making maps and when just flying around. Ever since the last patch, it's LOADED with errors. I mean, The Lego factory has less pieces of lego's then there are errors now. Most of which are loaded around DX11BACKEND, and WORLDGENERAL. Again, there were always a few, but now it's off the hook crazy loaded with these errors. Also, I'm used to seeing a few woShip referencing "SHIP_NOSE_ON_WATERLINE_CENTER or SHIP_TAIL(etc) - Now I'm loaded with this as well. Not to the degree of BACKEND and WORLD, but yeah, way more than normal Take a room, fill it with 10 people. All of whom get along (maybe a small argument here or there, nothing serious). Now, remove 1 person and replace that person with someone else. Now, all 10 people are having problems, not getting along, yelling at each other. Do you look at the 9, or the 1? Just asking. dcs.log-20181223-232650.zip

.

Rocking as always Grimes! Thanks man!

Try looking in the dcs.log file itself. DCS may not be building you a crash report, but there might be something in there near the end

Include your log files. The more information everyone can give DCS the more than can narrow down if it's ED issue, or MODs issue \Saved Games\DCS.openbeta\Logs

DCS Install folder>Mods

Do you have the mod MB339? If so, did you delete it, or just do something to disable it?

I peaked at a couple other logs from people, and will eat my words - I see where MODs are considered and why (makes sense in other words) - I still don't feel that's the issue. Other than MOOSE, I run no mods, and MOOSE is just a scripting language that works off of DCS's own API's. I wont speak further to that as I'm not smart enough to. But, what I will speak too is this is obviously something in the ED code/programming. When nothing else changes, the only thing it can be is the ONE thing that did change - DCS World

Not the exact same error I and some others are getting. It's an Access Violation - It's a memory problem. Two things trying to use the same spot in memory. Having the same problem, already posted about it and have already been told my NL that FlightControl needs to look at it since it happens during a MOOSE call (but nothing has changed in MOOSE). Put in a bug report with MOOSE as well. FC probably wont see it until tomorrow

Not asking ED to TS MOOSE, asking ED to take a look at what they changed around the engine shutting down or spawning of an aircraft. MOOSE hasn't changed anything in about a month (the release version, which is what I'm using, and have been for the last month) and it worked, again, FLAWLESSLY for me UNTIL the patch. Now it crashes when the engine shuts down, the plane is removed from the map, and new one is to be created. Somewhere in there. Not sure why MOOSE would have to TS something when they've changed nothing? (but they have been informed of the issue so they can look at MOOSE) *edit* Was the log even looked at? It's an interesting one - Separated part of it 2018-12-21 23:25:38.687 INFO EDTERRAINGRAPHICS41: surface5 gc() 10.993911 ms 2018-12-21 23:25:40.122 INFO SCRIPTING: 10954( 10856)/I: DATABASE00003._RegisterGroupTemplate({[Coalition]=0,[Category]=0,[Group]=IRAN#001,[Country]=34,[units]={[1]=IRAN#001-01,},}) 2018-12-21 23:25:40.125 INFO SCRIPTING: 10765( 10867)/I: DATABASE00003.AddGroup({[1]=Add GROUP:,[2]=IRAN#001,}) 2018-12-21 23:27:25.542 INFO SCRIPTING: 10954( 10856)/I: DATABASE00003._RegisterGroupTemplate({[Coalition]=0,[Category]=0,[Group]=IRAN#001,[Country]=34,[units]={[1]=IRAN#001-01,},}) 2018-12-21 23:27:25.545 INFO EDCORE: try to write dump information 2018-12-21 23:27:25.548 INFO EDCORE: # -------------- 20181221-232726 -------------- 2018-12-21 23:27:25.549 INFO EDCORE: E:\GAMES-SSD\DCS\DCS World OB\bin\DCS.exe 2018-12-21 23:27:25.549 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 8978333C 00:00000000 2018-12-21 23:27:25.550 INFO EDCORE: SymInit: Symbol-SearchPath: '.;E:\GAMES-SSD\DCS\DCS World OB;E:\GAMES-SSD\DCS\DCS World OB\bin;C:\WINDOWS;C:\WINDOWS\system32;SRVC:\websymbolshttp://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'Game' 2018-12-21 23:27:25.550 INFO EDCORE: OS-Version: 10.0.17134 () 0x300-0x1 2018-12-21 23:27:26.122 INFO EDCORE: 0x00007FF68978333C (DCS): (function-name not available) + 0x0 2018-12-21 23:27:26.122 INFO EDCORE: 0x00007FF689782E95 (DCS): (function-name not available) + 0x0 2018-12-21 23:27:26.123 INFO EDCORE: 0x00007FF6897C4775 (DCS): (function-name not available) + 0x0 2018-12-21 23:27:26.123 INFO EDCORE: 0x00007FF68977AD5C (DCS): (function-name not available) + 0x0 2018-12-21 23:27:26.123 INFO EDCORE: 0x00007FFBC7BF271A (World): (function-name not available) + 0x0 2018-12-21 23:27:26.123 INFO EDCORE: 0x00007FFBC7BF2C06 (World): (function-name not available) + 0x0 2018-12-21 23:27:26.123 INFO EDCORE: 0x00007FF689A31986 (DCS): (function-name not available) + 0x0 2018-12-21 23:27:26.124 INFO EDCORE: 0x00007FF689A3FF4E (DCS): (function-name not available) + 0x0 2018-12-21 23:27:26.124 INFO EDCORE: 0x00007FF689A18530 (DCS): (function-name not available) + 0x0 2018-12-21 23:27:26.124 INFO EDCORE: 0x00007FF689693DD5 (DCS): (function-name not available) + 0x0 2018-12-21 23:27:26.124 INFO EDCORE: 0x00007FF689695C09 (DCS): (function-name not available) + 0x0 2018-12-21 23:27:26.124 INFO EDCORE: 0x00007FF689BCC44F (DCS): (function-name not available) + 0x0 2018-12-21 23:27:26.124 INFO EDCORE: 0x00007FF689BCC44F (DCS): (function-name not available) + 0x0 2018-12-21 23:27:26.124 INFO EDCORE: 0x00007FFBCEF93034 (KERNEL32): BaseThreadInitThunk + 0x14 2018-12-21 23:27:26.125 INFO EDCORE: 0x00007FFBCF553691 (ntdll): RtlUserThreadStart + 0x21 2018-12-21 23:27:26.342 INFO EDCORE: Minidump created.

Can confirm, exactly that same error here. Nothing in MOOSE has changed and can confirm the night before the patch it worked flawlessly (was helping someone debug something around the InitRepeatOnEngineShutdown and used it perfectly in about a dozen tests). Next day, patch, boom, this. We are letting FlightControl know so he can double tap on his side, but unless ED changed the way it works, there should be no issues with MOOSE dcs.log-20181221-234413.zip

This - To orbit in a circle, you need one way point. Race track is two. I have a Predator that I tell to orbit and it does a perfect circle around one way point. I use MOOSE to get it to lase

Also, you state above that Wind Over Deck shouldn't be more than 30knt, but on the vid, you said any speed? (see attached). Is the final tweak going to be 30kt then slide? Which I agree would make more sense that say, 70knts and still no issue (though I would think you have other things to worry about at that speed lol)

yup, just had a buddy slide right off the deck into the ocean last night. It's still happening. No, I don't have a track, so I guess I'm lying? (sarcasm, sorry. Just don't know why we aren't believed unless we provide a track. does the track provide more information other than to prove we aren't lying?)

I know this is an old thread, but any word on this? I'm having this issue as of today (21 July 2018)

I run into this ALL the time (but if you ask Franky, I have too much going on in my maps lol). But yeah, it's bad d s logic. Harriers are the worst. They get stuck on the Tarawa all the time

I've always found it to be a Problem with the folder name. I ways remove anything trailing _ ie MOOSE 2.3.1_blah lah blah. If I rename it to MOOSE 2.3.1 it sets up with no build errors

How would you go about getting a ship to follow the Stennis? Or any other ship for that fact? I know it's been brought up, but I can't find anything on how to build something like a carrier group? Build the carrier, set it's way points, then toss in 4 or 5 other ships that just follow it around. I know you could just add way points and set the ship speeds the same, but after time, as the ships turn, the others would fall away or get ahead (depending on if they were on the inside or outside of turns)

Which is kind of what I was after, but I see your point. Your first example I read once and got it, your second I had to re-read it because I thought it was wrong but see where it's right, and also see your point ;) Pick your battles is what it boils down to ;) Appreciate the advice!

Shouldn't be any different on M, but I change actuall channels (1, 2, etc)

Ok, I didn't think so on the last one ;) and I didn't realize it wasn't available in RAT yet. I made the assumption that because it was within MOOSE it could already do that. My RAT file is huge with little one line code and was just hoping to tighten it up, kind of define everything in one shot/on one line ;) Once again appreciate the help (and the RAT!)

Instead of this - local AH64 = RAT:New("RAT_AH64") AH64:SetCoalition("sameonly") AH64:Spawn() Would this be advisable - local AH64 = RAT:New("RAT_AH64"):SetCoalition("sameonly") AH64:Spawn() or even local AH64 = RAT:New("RAT_AH64") AH64:Spawn():SetCoalition("sameonly") End goal - Trying to tighten my code up. This, above, isn't big, regardless of the three chosen, but, when using the 1st one (which is how my script is), and I have a LOT of aircraft, I see a LOT of wasted space, just in the :SetCoalition() section (needless to say every other section). As I learn things, I like to spell them out, step by step, but once I start getting them down, I like to make it smaller and smaller, executing only exactly what's needed. And I posted this here instead of in the RAT area because it's more a LUA/MOOSE question than it is a RAT question, I was just using that as my sampe

So, whenever I start my map, and jump in as a spectator, it always starts in exactly the same spot. It used to change after I'd place an object and then it would start at the last place object. It no longer does that. I have NO idea how it was moving around before. So, my question is - Is there a way to pick where you want the camera to be when you load in and you haven't F2/F7/F9/F12/etc etc yet? I'm tired of looking at exactly the same back end of exactly the same aircraft......