Recluse

There is, indeed no going back. Here's another cool VR thing. Eject while sitting on the runway and just walk around and marvel at your jet from the outside with the POV of a person-sized object on the ground vs. the usual outside camera view.

I have benefited greatly from your training missions on various aircraft, so it makes me VERY happy to have been able to give back to you!!

Could it be a potential side effect of the new "sanitization" of the dostring command? Did you try putting in the autoexec.cfg in this thread?

In this situation, I have done the following: Set the LST to the JTAC code, acquire the spot, designate and prosecute using my own laser set to the code for the bomb. Of course, if you are not carrying a TPOD, this won't work, but from your post, it seemed that you were.

@cfrag I hope the wounds heal and your passion for this stuff brings you back to us someday soon. DML is a great contribution to the community of Mission Builders who choose not to become LUA literate and provides so much capability for building diverse and complex missions.

Yup!!! That's where I was going with my original post. It seemed to me at the time that it made sense. Kind of like a "poor man's laser spot tracker" similar to how you use the Laser seeker on a Maverick-E which starts scanning even before there is a spot to find. Just as you describe and where my head is at!! I will have to try this. Generally we get some external information that there is a buddy/JTAC/FAC lase, so there is another cue to make SKR the ACQ Source

Glad this observation was helpful! I have no clue as to your question about the other theaters. Maybe @cfrag will have a more informed opinion.

Well I don't have the Germany map, the Corsair or any of the campaigns, so maybe that's why?

This update downloaded and installed EXTREMELY quickly. Is it really that small or was stuff missing?

Don't know if it is relevant but there was a scripting "fix" in today's update: Scripting API. Changes to the behaviour of net.dostring_in(). This API can be used only with trusted scripts/missions! More details here: Changes to the behaviour of net.dostring_in() - ED Team - ED Forums

Maybe some combo with WilliePete? Allow the player to create WilliePete zone on the fly, so not as easy as marking a point and having artillery fire, but marking a zone and then needing to fire WP rockets to call in the arty?

I will send it to you. No Mods, just a Hornet which I can remove and replace with an SU-25T. Been building this up so it has gotten kind of busy.

@cfrag Hmmm DEMO works fine, but my mission throws these errors: Zones are clonezones (currently RED) with mixed Static/Vehicle with attributes. Scout is a Blue aircraft. Originally I stacked the recon attributes into the Clone Zone, but then I created a separate recon zone just in case that was causing the errors recon stat dynamic true

THANK YOU!!!!! That was quick and seems like an elegant solution allowing for much flexibility!!

Thanks for mulling it over. I guess you guys in Europe can get real Absinthe? I think it is now legal in the US but only with very low Thujone levels (10 mg/L) https://www.mashed.com/209498/the-reason-absinthe-is-no-longer-banned-in-the-u-s/ Some time ago I got a bottle of Versinthe which claimed to be close, but was mainly anise and herbs and ZERO Thujone. Of course from what I have read, the effects of Thujone even at the relatively high levels in the heyday of the Green Fairy were not really as intoxicating or toxic as believed. Mainly the high alcohol content. But the Nanny State will have its say!! Back to Static Recon Targets: I was thinking that to avoid the overhead, maybe Statics could ONLY be re-conned when inside a PRIORITY TARGET Zone. That would limit the detection of eye candy statics. Possibly the same for Map Objects, though, personally, Map Objects are not a priority.

Thanks!! Stay cool!!

@cfrag Started messing around with the Recon Mode module. Originally posted some bug reports but on further testing, everything is working as expected. Question though: - Any way to include Statics in the report (e.g. reporting FARPS, structures etc..) or would this be too resource intensive. Not suggesting built in Map objects, just Mission Editor placed statics.

Yeah, I would be comfortable with the process, my concern was whether or not my particular flavor of the Z490 would support one of those BIOS options since the board seems to be a slightly different version made for the Chinese market. Since the BIOS does seem to be for 7C98 boards, it is probably fine. However, I ran into another snag since I also need to update the VBIOS on my ZOTAC RTX3070 and ZOTAC no longer has this board listed on their site, nor the BIOS updates for it. I found some newer VBIOSes on the Tech PowerUp site, but not 100% sure of compatibility. Since it doesn't seem like it does much for VR, it probably isn't worth the hassle. That said, my Bios and VBios are Really OLD and there are probably other advantages to updating them!!!

I meant, can a non numerical flag be used in an artillery zone: in? "StartShot" vs "100" Again, the answer is YES.. I misunderstood this as meaning it had to be a NUMBER, but that was just pointing out compatibiity: null

THANKS!!! Always good to know I wasn't missing something obvious. Latest manual still had the f? shown, so I didn't know it was deprecated. While I have your attention on artilleryZones, a few questions if I may - watchFlag (f?. in?, artillery?) shown as NUMBER. Does it still have to be a numbered flag, or can the usual DML flag NAMES be used? - I should just try it, but I will ask anyway: Can multiple artilleryZones use the same watchFlag? e.g. Simultaneous bombardment on 2 (or more) sites using a WatchFlag with Flag 100 Never mind, I tried it and answer is YES.. and the new artilleryZone.lua works perfectly!

@cfrag I was trying to use ArtilleryZones and kept getting the first error message below I figured I was doing something stupid as usual, as your demo mission with triggered Artillery seemed to work fine. THEN I tried substituting the LATEST cfxZones.lua into the demo mission, and got a similar error (which persisted when I also updated the artilleryZones.lua I did leave the value of the artilleryTarget parameter BLANK since the manual said it would be ignored anyway. EDIT: Interestingly looking again, I don't see a starting message that artilleryZones.lua even loaded. I created the simplest mission I could think of and still got the error and didn't see artilleryZones loading, though I definitely did on the stock Demo mission. I retrofitted the old version of artilleryZones to the mission and it loaded without error and worked. Something off in the new version??? simpleArty.miz : Older (2.0.1) artilleryZones simpleArty_V3.miz: Latest (3.0.0) artilleryZones null null simpleArty.miz simpleArty_v3.miz

Indeed! I dug a little deeper and though my Motherboard is a MSI Z490 PLUS, it is apparently a CHINA only Motherboard (MS-7C98) that MicroCenter used in their PC's. Doesn't look like there is a REbAR compatible BIOS update for this board. So I guess I live without Resizable Bar! https://community.microcenter.com/discussion/6357/bios-update-for-g436-msi-z490-plus-mb/

Thanks for the clarification... I thought that might be the case, but wasnt sure if NVCP was reporting the actual state or the support. When I checked on my Motherboard BIOS support, at this link, it indicated the NVCP item was showing GPU support for ReBar https://www.msi.com/blog/unlock-system-performance-to-extreme-resizable-bar Maybe there is a difference between HARDWARE support and VBIOS support?

Dumb question maybe,would resizable bar have any effect on VR performance? It does not seem to be implemented in my BIOS, and I am getting contradictory information on the GPU: GPU-Z says YES, Nvidia Control Panel says NO. Before I start jumping through hoops, I thought I would ask if it has any effect in VR which is where i usually spend my DCS time. Note: I did enable in Nvidia Profile Inspector, but no change in the report from Nvidia control Panel. nullnull

The Date Modified on the Hook script was from back in April, while the Qwerty/Coordinates were from June 7, 2025 so I didn't think it was updated: But I found I was using an older one anyway, so updated! null