RepoManR6

Thank you for reading. The first video is basically the issue I described with the 114K+ Brauning Loadout Issue 2 - OH-58D AGM 114K+ Brauning Loadout This second video is of issue 3+4 listed: SA34L 20mm gun run with +4 AP + 1 HE. I have similar results with the F-16 and I have seen some videos of F/A-18 gun runs with similar performance. I'll dig around for my recorded data. I'm in the middle of mission development. Thank you once again. SA342L 20mm gun run - soft skin

I'm a little confused. Is the OH-58D only in mission editor for DCS World Beta?

OH-58D| 1. The model itself, the doors keep coming open during flight. OH-58D| 2. The mission payload with two AGM-114k, and the OH-58D Brauning pod cause flight issues. The helo sometimes doesn't take off especially after refueling. Secondly, there is just odd behavior when using a FARP for refueling. SA342L| 3. The GIAT M621 when fired, sounds like a M61A1 Gatling. SA342L| 4. AP combat mix has limited effectiveness on soft skinned vehicles. (I noticed this for the 20mm for the F-16 in testing against different targets. I have data I will post in another thread when time permits. Thank you, *If needed I will follow this thread up with video. Syria helo testing6.miz

Finally! Looking forward to this.

I know there are ways to set this up, but it would be nice if there was a baked in tick box for a unit ai to be immortal to other ai except to player/client ordnance. I like to use this option for ground units to show a sustained firefight. I know there are ways to set this up as is, but I think there could possibly be an easier way? * Other wishlist items is an Ai Little Bird to replicate 160th SOAR, and modern looking JSOC infantry units with IR on their uniforms. * Cargo birds such as the C-130 being able to drop some type of cargo crate with chute. If this is already implemented for the ME then my apologies. Last time I checked it was not...last year I think I like to design missions without ctld, or other mods. I notice they last longer through updates. Thanks

Thanks for pointing that out! That's kind of weird.

I was wondering about this too. So for me in SEA mode I can find my targets (stationary) however I can't designate them unless in expanded mode. In expanded mode ships are not really white but darker images (they are harder to see in contrast) but can still make them out. After I designate them, pressing the TGT doesn't slew the TGP automatically which is a real pain. With recent updates pressing the TGT button now cycles through two other things and I can't find any information on what is does. I can't remember what it's called. maybe TGT, DSB1, DSB2. i JUST remember one and two accurately.

This is an annoying issue. I have been battling this problem for some time. Is there a remedy? I have tried numerous suggested fixes. Is it because of DX11? I keep hoping for some update that corrects it. System Specs: 64GB Ram 9900k Oculous Quest 2 3080 12GB

After reviewing hours of of what the server admin thought may be my flight - it isn't. I haven't had issues since the latest update, but will keep my eye open. One thing I have noticed is that INS/GPS guided weapons have to realign when you re-select them in SMS, post turning them on and having an initial alignment - for example switching from a HARM in flight. Is this normal as I am transitioning from the A-10C II and there are a lot of unbalanced attributes related strictly to the F-16 compared to the F-18 (bore alignment of mavericks). Thanks

It's the same for Viper and I just noticed in A-10C II also. Ummm, is this right?

I noticed this since the update

I was able to obtain a track file from the server admin. Let me review.

1. I was playing online trying to sneak up on an enemy airbase with my RF switch in quiet mode. My CBU-105's were powered on prior. When I reach the target I got one release and realized I was in quiet mode = bad drop (Pre mode). I turn it on and I could not get another pickle. I move off from the target area and switched modes to vis, back to pre, and even switched weapons then back to the cbu = Would not drop. I power cycled them, turn my master arm OFF then back on, cbu's showed RDY and was able to pickle. Next drop in sequence after another pass, cbu's still showing ready would not drop. I followed them same procedure of power cycling, Master arm on and off, then back on resulted in a successful pickle. I had one more CBU-105 left for a pass and it would not drop. I jettisoned the weapon and RTB. I noticed other instances where they haven't released and there won't be a falling cue. Only the weapon in range carrot works. 2. With this being in VR and online multiplayer I don't have a track. I can possibly submit logs? 3- 4- Multiplayer - Caucasus 6- I searched and found a similar report, but not very detailed.

Hello, I was wondering if anyone knows of any written tutorials or downloadable templates for creating SAM sites. I know there are videos out there but it would be nice to have something for a user to have the ability to create something simple to complex and what units are needed with an element of understanding. I know there are videos out there but some of them lack information on what you are actually doing for the "why." Also some of them are lengthy. It would be nice if there was a guide or manual including unit profiles etc. The DCS World manual I don't think has been updated in some time. Questions: From my understanding at the minimum you need a radar, then launchers for something basic. Correct? Do you need a command unit? What are some some standalone SAM units? I'm assuming if they are under "player driveable" they can act on their own. Forgive my lack of knowledge on this. of this concept. Most video I found people are creating really complex large sites. Thanks.

So I resolved the DSMS issue and tried to figure out a way around the no spi issue from a cold start. I tried selecting a waypoint via TMS as SPI. I read somewhere entering the elevation for each waypoint in the CDU may correct the issue. Selecting Hot start from ramp resolves it. I went further to try to find a solution by going through the .miz avionic lua files comparing them for anything related to SPI seeing if anything stood out. I came up with nothing. Personally I'm tired of recreating planes and way points when I need to move on to testing the mission further in it's timeline of triggered events. I would appreciate anyone from Eagle Dynamics or with some familiar know how to chime in on the issue.

DSMS settings.lua file that's corrupted SETTINGS.lua

It happens right after selecting "prepare mission" from the Mission Editor starting from ramp. I do believe I also tried it while selecting the initial starting point as a "fly over" start with the same results. Somewhere during the save progress of build a mission I think something gets corrupted. I usually create a new save file every so often to prevent .miz file corruption. - Selecting a Ground Crew rearm and reloading DSMS doesn't resolve it either I might add. The DSMS issue possibly is initiated after saving a mission in the Mission Editor. I remember this happening years back as well. It's strange because I will save it manually before selecting preparing mission, then when selecting "prepare mission" it will warn me that the mission wasn't saved (even after I saved it). So I will re-save until ME is satisfied after selecting "prepare mission. Mission Editor sometimes asks for numerous save requests. I tried numerous work arounds for example; selecting a pre-selected loadout. It still happens. Only deleting DSMS in avionics corrects it from the .miz file -> which leads to the SPI being lost. Regarding the SPI being lost on this corrective measure: I found a couple other reports on the "No Spi Error" on other forums after using the *delete DSMS* procedure from unpacking the .miz file.

I have been working on a short mission to share with the community and I'm almost done. There are a couple problems I keep running into. 1. The DSMS (A-10c-2 keeps showing red weapon stations when there are indeed ordnance there. This has happened before. *T1: Corrective action: I'll unpack the mission and delete the DSMS in avionics. I then repack the mission and load it up in ME - then choose prepare mission. This corrects DSMS *T2: After the process of resolving the DSMS stores, I get an error on the (white box message) that there is no SPI. - Attempted corrective action. Deleting the waypoints. One thing I have noticed if I selective fly over point instead of the "ramp start" this message does not appear. Question: Is there a correct way to resolve the "No SPI" error after deleting DSMS avionics folder? I have searched and I didn't get a lot of answers. Thanks

Thank you so much. I chose player for the spare planes. I'll make sure I choose clients next time.

I noticed making missions for practice I would place aircraft for modules I own so I could choose what aircraft I want to fly and practice with. Next thing I know jumping into the mission only to notice an AI grabbed a plane I wasn't using and flew off. Am I setting something up wrong? Is there any way to prevent this from happening? Anyways I proceeded with the mission and forgot about this rogue jet flying around and ended up shooting it down by accident for a blue on blue.