fargo007

Vietnam or Iraq/Kuwait.

I thought this would be more than apparent, but if you can't see the value, sure. ScratchPad As I am testing, I make quick notes of coordinates, places to shift assets to, things that have to be copy-pasted into map marks, etc. And they still appear on the screen in the ME unlike the non-persistent marks. VoiceAttack I use this for automating functions that I am testing while creating nested structures of menus, or anything that requires numerous sequential keypresses or inputs. Having it walk the CTLD or CSAR tree and test your pickups is a great example of using this to save time and speed up mission development. FPS VR Quite obviously - for checking the frame rate in your missions for performance. Identifying possible objects that are producing too many draw calls and tanking your frame rate. I have this on literally all the time.

This list bears repeating.

They did extend it, but it was because it wasn't doing the same amount of damage they expected, based on other 30mm platforms. The longer barrel produced an increase in muzzle velocity which made the rounds hit harder.

The title of the topic is "How to Ground Re-Arming and Re-Fueling." Pointing out that a FARP object is required for this is absolutely relevant to that. Thanks for the nonsense dissertation anyway.

As we were flying around last night, the characterization "out of the park home run" seemed to fit best. Please congratulate the team on a really fantastic job. You guys have outdone yourselves.

This is not the case since a few updates ago. I have submitted code to the CTLD github to model the weight of troops in CTLD. It works perfectly. The function is: setUnitInternalCargo(<String>unit, <int> weight)

WHOOHOO!!! This is exactly what I was hoping for. Thank you!

I can route a ground unit to a vec2 very easily, but I'm trying to expand that into (n) destinations past that. Anyone have a technique in MOOSE to pass a route to a ground unit that essentially hands them a series of waypoints to follow? Hoping there's a simple solution I'm overlooking. Thanksbros!

It doesn't matter. Make a C:\Scripts folder and extract it there for instance. When you load it in the mission editor, you will have to navigate to the location where you've placed it.

I would imagine yes it would be. Especially because flying fixed wing once airborne is orders of magnitude easier in a modern fighter aircraft. Landing may be a bit of a different story though! :pilotfly: It's really a testament to the accuracy of the flight models in DCS, and the fidelity that they have put into the aircraft. Any one of the guys I fly with in squadron could have done the exact same thing. At least as far as the basics, DCS can give you the monkey skills 100%. And DCS was superior in more ways than one. Based upon what I saw, if they had a physical cockpit that lined up with what you see in VR, such that the pilot can actually flick the switches and turn the knobs physically, and modeled the hydraulic forces on the controls, it's game over for these multi-million dollar, huge hydraulic tractor-trailer sized sims.

I've never taken a helicopter off or landed one in real life, but have substantial experience in DCS/VR. I got over a half hour of time on a military 206C sim. Not only was I able to "fly" it, I was able to do so very precisely, and even to hot dog with it. Turning about the nose, landing on top of a small building, on an LHA, all of it. I was assured that flying this sim means I could fly the actual helo. DCS works for this purpose, and it works well.

It's not possible to rearm/refuel WITHOUT a farp object.

Yup, it's supposed to be seconds. I don't remember ever seeing this feature work correctly.

In the assert you may have to escape all the backslashes. e.g. \\Path\\to\\My_Scripts_Directory\\script.lua Watch the dcs log for the error which should be helpful.

The skin may be locked to certain coalitions/countries. Run through a few different nations to see if it's there.

Other than at an airfield held by the same coalition, no.

Looks like no multicrew update referenced in the changelog. :-(

If you use MOOSE SCORING and assign a value of 1 to a destroyed target you'd probably be quite close. There's no way I know of to access the data you're showing.

MOOSE has a SCORING class that you could use independently.

I want multicrew like a fat kid wants a second slice of cheesecake. :D

It doesn't expose a public URL by default, though it may be possible to configure IIS to expose that URL. I've not seen that done and have no information on how to do it. We use slmod on our servers which allow authorized users to change/restart missions, and it works great.

Props to you Chic for coming up with this. It's the very best way to drive CTLD/CSAR operations that I've seen. Arguably the most realistic, since the pilot would be actually speaking to make this stuff happen, not clicking buttons and things.

My technique for lining this up is to use Rctrl-Rshift-keypad\, *, 4, 6, 8, 2 to shift the center position back, fwd, left, right, up, down until the huey's stick is centered on my own. It really ups the immersion for me to have the correct perspective.

No way to make it consistent. We do automate it though via voice attack commands. A user named Chick came up with a voice attack profile that allow you to do this after two brief setup commands in which you tell it which item is CTLD and which is CSAR. I don't have permission to share it forward you will have to look around.