Recluse

I am wondering if they introduced some new bugs.. Luckily I didn't see any issues crop up in my DML enabled missions, but I wonder if there was something done w/re to internals. Possibly unit state checking or something....I was flying one of my missions using CTLD JTAC Autolase and the messages I was getting about target destruction and target switching seemed to be multiplied. Didn't get to check DML REAPER in this regard. Regarding DML Reaper:. I have complained in the past about ordnance not guiding consistently, but yesterday I realized that I had used an altitude parameter of 15000 forgetting that this unit should be METERS not FEET. I cranked it down to 5000 so I will see if my problems go away. Makes sense it was a ME problem all along

Recently noticed the "Neutral (takeoff) trim in pitch, roll and yaw indicator lamp" Just wondering how it is best used in flight. I can sort of guess from the name but noticed the lights going on and off in normal flight and wondered how to interpret them. null

OOPs... I saw a lot of SU-25T content in this forum, so I used it...but I did realize that it was under the FLAMING CLIFFS section. Will check out the other one for any further questions. Yeah I thought about the contrast issues but I figured they would have been tweaked to be optimal in the TRAINING MISSION where I first encountered issues. Seems to be working OK for me now, though I struggle a bit Will probably not fly this A/C too much but I figured after all this time I should at least TRY it

I will make one shortly. Thanks for the reminder! EDIT: Had another go at it and it seems like things are working as expected. Not sure why I couldn't get it to work. Still have to work pretty hard and get pretty close, but at least it is working!! Sorry for the false alarm.

Probably just a Git Gud problem, as this is the first time I ever decided to try out the SU-25T, but I was wondering if anyone else had trouble getting the SHVAL to "snap" to target (AC) in VR. (I guess I should go try it in 2D to see if VR is really the issue) Was going through the original tutorials and also trying it on some home made missions. Having a really hard time getting the target to snap on even with messing around with the target box. Usually with vehicles. Seems like I can get it to work with larger things on the ground. Doesn't seem to matter how close I get, what size the box is, it just won't snap, and TV guided weapons will miss even when LA is achieved.

Yep, that is what I meant, and the answer I expected Similar to the Demo mission on BFM using moving clone zones linked to a Player Unit, but wondering if it was in any way possible to link to a Dynamically spawned (DCS Multiplayer Dynamic Spawn) player when, of course, you didn't have a UNIT NAME for the linkedUnit parameter.

@cfrag et al., Wondering how DCS treats Unit names for Dynamic Spawns (both in the case of Templated spawns and non-templated spawns). Pondering the possibility to apply moving (clone) zones to Dynamically spawned aircraft e.g. to have a spawnable Escort, or even opposition flight in the vicinity of a particular Player unit at some given time.

Just following up: Based on limited testing, (LOL N=1) I believe that my Reaper issues may also have stemmed from using a client that was part of a multi unit group (even though only 1 was active). When I switched to single unit aircraft groups, the laser targeting seemed to be working better. My little brain can't quite figure out how this could occur, and I will continue to test.... Edit: Sadly N=2 showed same behavior. Reaper laser sometimes does not guide weapons correctly, Meanwhile, I have a couple of QOL suggestions for the Reaper module: - Add a flag or UI item to allow the player to release the Reaper from use once all targets have been destroyed and/or - Add a time parameter to allow the mission builder to give the Reaper finite Playtime, so after (e.g. 30 minutes) the Reaper "departs" Not having infinite Reaper time would make the bank account more important (if a mission is using that function). Speaking of the bank, I couldn't seem to find a way to retrieve the current bank balance (other than buying something (pretty much only the Reaper at this point) and seeing the balance.

I think I figured it out. When I spawn in a SINGLE aircraft everything is fine whether it is manually placed in SP or Dynamic in MP. IF, however the client aircraft are in a group (in this case 2 aircraft), the doubling happens, as I guess the stats are seeing 2 aircraft at once? Maybe I missed this caveat in the documentation.

No joy Did a proper Do Script/copy/paste and same thing. I even checked the .lua to make sure it wasn't doubled but it didn't seem to be. Interesting, though, in the VERY SAME mission, I started in MP mode with a Dynamic Spawn and everything was fine. Single Player with a manually placed aircraft gave me the doubler. On a related note, should Valet work with a Dynamic spawn? Edit: It does if you remember to set greetSpawns

I will try, but being a lazy guy, I used do script file instead of copy/paste, but maybe I messed up the file initially.. Will try and report back!

@cfrag Don't you just hate it when I try modules I haven't tried before and bother you with questions?? Yup I'm at it again. Running persistence/scribe. Scribe stats get saved and I see them as initial greeting. All good. But I don't understand why I have 2 Mission Logbooks And under one of them I see 2 Statistics entries, but NO statistics are shown from either one. Basically nothing happens when I click. Under the OTHER one, there is nothing I checked for double loads of scribe module, but that doesn't seem to be the case. I have only flown as one pilot, but have flown different aircraft, and in some cases, the aircraft were in a group of 2 (clients) and I may have flown each one at some point. scribeConfig shown at bottom

@cfrag Hate to pile more on your already overflowing plate... but if you have some spare cycles, could you look at Reaper.lua? I am having very variable results, where it seems that it should be lasing but weapons don't guide. I know it is possible for them to lose lock, but I don't get that message. I have locked an AGM-65E onto a spot and it plummets right into the ground. Likewise I have dropped a GBU-12 and it falls ballistically without guiding. If I turn on my own laser, they guide fine, so I know the code is right and all the fuzing etc. is good. Odd thing is sometimes they guide perfectly. Maybe just a case of momentary target loss, but my LST shows a lock on the spot throughout the engagement.

@DD_Friar Did you by any chance try the new groundOnly flag and see if it worked? As you have seen it didn't (quite) work for me, the way I expected, but now I don't trust my system at all!!!! I have taken your idea to heart about unitZones. Only problem (and this might be something I am just doing wrong) is I miss Valet's ability to pass the <p>, <u> and <type> wildcards to messenger. I could not make this happen with unitZones (as the zone isn't quite as aware of who is in it as valet., but it is very likely I am missing something) @cfrag Wow!!! THAT SUCKS.... At least I am not CRAZY (well, in this particular instance, anyway)

Indeed I do have the Herc mod installed! It isn't in any of the missions that have been causing me this headache, but the mod is definitely installed. Edit: I just retried the demo - being persistent.miz and this time IT saved to tempMission (data)/tempMission.txt as well!!