HawgDawg4Life

Here is the mission This is a copy of the mission I created to reproduce the situation. To test it both ways, add and remove SAM Sites. When they are in the mission, SA Crash, when they are not, NO SA Crash. sa_test.miz

Oops I tried to attach the file to the last post but it was 1 mb larger than the alotted 9.? mb. So I busted the track files into 2 zips. 5 Track Files.zip 2 Track Files.zip

7 Track Files Here is a Zip file with 7 track files in it. If you arrange them by date, the latest one is a SA crash the one before it is no crash, the one before it, Crash, the one before it, no Crash. It is all based on whether or not I put SAM's in the Mission.

Upon Further Testing I can confirm that the SA page Crash is directly related to having any SAM that produces a Dashed Range Circle on the SA page. I have tried this with the SA-8, 6, 2, 3, and one other. It doesn't seem to matter what puts the range indicator on the SA page. if its in multiplayer it crashes my DCS.

Ok. I have some Real Info Ok, So It dawned on me and some of my buddies that all of the servers I connect to seem to have SAM's in them. So My buddy says, create a mission with no SAMS and see if it still happens. Brilliant suggestion, I thought. So I did... I created a basic mission with a few yaks, an AWACS, Some Dumb Ground Troops and an F-18. (NO SAMS) I run the mission Multiplayer and I do NOT have an issue. I even flew out, killed the Yaks, Blew up the ground units, Talked to AWACS, Ejected several times and got into a new plane. Still, the SA page displayed like a champ. Instantly upon press. Like the problem doesnt exist. I then Opened the Same Mission in the ME and added 4 SA-8's to the map. I fire it up again and in my first sorte, on the ground during startup, as soon as I press the SA button on one of the MFD's My RAM filled up and my DCS Crashed. This seems to be related to SAMS and the SA page. I havent tried other SAMS, like the 6 or the 11, but I will be doing that. Definately happened when I added SA-8s.

Watching Memory OK, so I finally opened my resource monitor while running DCS to watch the memory usage. DCS consistently uses about 18 gig of my physical memory, which I have 24, so it shouldn't be an issue. Well, until I press the SA page. Anything else that I do changes nothing in memory usage outside of 5% variances. However, when I press the SA page and the game crashes, my Ram usage jumps from 18 gig to 40 gig, like instantly. This only happens if the SA crashes my dcs. If I get lucky, like the first time I launch the SA page everything works fine and there is no spike in physical memory usage. But, the second time I jump into a new plane and fire up the SA, Boom, 40 gig usage and crash.

Your on Target I too thought this was the case, but from time to time, I can get the SA page to come up and show rings around my area like SAM engagement zones, that I KNOW are not there cuz I created the mission. When I see this, I know that the next time I select the SA page I am going to crash. This happens when I select the SA page when only one engine is started and as soon as I start the other engine and select the SA, Boom! Also worth noting is that I can avoid the SA crash once in any given mission by selecting the SA page during startup and before I am finished starting. But then, If for some reason I need to load a new aircraft, it is guaranteed to happen. Also, Even if I restart DCS completely it is guaranteed to happen. Im telling you, this smells like a memory leak.

its baaaack.... Well, I thought I had some success, but it didnt take long for the problem to resurface. I kept getting low on virtual memory error in Event Viewer (and still do), so I increased my VM to 64 gig thinking, "I'll show you!" but it doesnt matter what I change it to, it still happens. I am guessing that there is a memory leak or that DCS is not releasing memory that causes this issue. I am looking into my GPU virtual memory now....

Wow and that god for old threads So I ran into this problem yesterday. I zipped up a livery I made to send to a friend and didnt delete the zip file after sending it. Then, in the editor, I couldnt add any hueys to any mission and the missions that already had a huey blew up as described here. Thanks (albeit belated) for this thread. lol

Missing Damage Model Entries Ok, So it seems as though I was able to get the paint to show up in the list, but when I selected it, it dropped back to the default paint. So I opened my Description.Lua File and everything looked ok, at least I thought. This paint used to work fine, but now, nothing. I opened some description.lua files from working paints. The only difference between those files and my Description.lua file was that they had entries for the damage module, where I did not. So I added the entries pointing the damage modules to the same paint and the problem was resolved.

Am I the only one? It seems to me that a key element to WWII is missing in DCS, and that is, the ability to drop paratroopers. Are we ever going to see a C-47 with the ability to drop troops?

C-47 With Paratroopers It would be nice, since a WWII campaign was built, if some C-47's were introduced with the ability to drop paratroopers on a battlefield.

Found my Fix So, this has been happening with me for a couple weeks. I thought I was the only one, until I read this thread. So I posted a couple days ago about my experience then, last night, it happened again. 'Ah Ha', I thought, I am going to track this issue down before re-firing my DCS. So, I start looking for a crash log, but none existed. I looked at my DCS log file to see what was happening before I pressed the SA button, still, nothing. Then it dawned on me that I needed to open my event viewer and see what my system said about the app crash. I look in Admin and found nothing that corresponded to the time of the crash. I looked in Applications, thinking surely there would be something there, but nothing. In a last ditched effort, I opened the System log and there it was, a single message saying that I was low on Virtual Memory that occurred at the exact time of the crash. So, I opened my Page file settings to discover that my page file was spanning multiple disks. 4 gig here, 4 gig there.... So I wiped out all the page files, rebooted, then built a little 3964 mb page file on a single disk. Fired up DCS, went into multiplayer, and walla, I could launch the SA page in the F-18 with no issue. It came up instantly. Don't be fooled, I said to myself, I have seen this before. DCS was playing games with me, cuz the second I go into a different server, it is going to happen again. I have logged into several servers, Yes server admins, that was me popping in, starting the 18, then popping out. I must have logged into 12 of them, but still cannot get the SA Crash to happen. So here is what I suggest. The next time you experience a SA page crash, note the EXACT time of the crash and start looking in your event viewer for a message that corresponds to the time, follow that rabbit and you just might fix your issue as well.

Also having this issue I am in VR (apparently it doesn't matter, but...). This started happening to me after a SteamVR update so I thought it was a SteamVR issue, but tested it without VR and the same issue. I went into NewB City and with the 18 I press the SA page and dcs crashes leaving the last thing I was looking at on the screen. DCS itself closed but he image remained. I restarted DCS and logged back into the same server. Same results. So I then log into TTI and the problem didn't happen. I thought that it had to be something wrong with the map on Newb City, but then I was on TTI a couple days later and the same issue occurred. Again, twice in a row.

The truth of the matter is that if you build it, they will buy! That being said, I would LOVE to see a UH-60 in Blackhawk, Seahawk, Pave hawk, and Jayhawk variants. Be nice to consider some coast guard options for S&R. The differences between variants is relatively minimal. Of course, would love to see the Chinook, CH53, CH46, and even the old MASH Unit CH47 with passenger baskets. Is it obvious that I am a helicopter guy?

AS if You speak of the liveries folder as if it exists. In my saved games\dcs.openbeta\ folder there is no such folder. I am at a loss here cuz I have ran a livery for the huey for years and now it dont work. I look in the saved games folder and there is nothing in the mods folder. I have the skin, but where the hell do I put it?

Well I didnt... My \saved games\dcs\mods folder is not empty. I had a nice skin that I have used for years in the huey and now its just gone. Of course, I have a copy of it, but where now do I put it in?

I am sure that this has been brought up before, but is there any chance that the embarking and disembarking engine could get looked at? At current, only the first person in a chopper (any chopper) seems to be able to embark troops. anyone who hops in a chopper after the first guy does not get the embarking option in the comms menu.

After extensive testing Been driving me nutz too.... The problem is worse than I thought. Not only is embarking locked to the first player in a chopper, it is locked to the first person in any chopper. So, I have a mission where I have huey's transporting troops for the US and Mi-8's doing the same for the Russian side. I jump in a (of 4) huey's and I can embark troops, but my buddy, who jumps in another huey can not. So I tell my buddy to jump into an Mi-8 and embark for the red side. He jumps in the chopper and still cannot embark troops. I, on the other hand can jump into the Mi-8 and the embarking works for me just fine. This is so irritating and I really wish ED would give this functionality a little more respect and time. It is a huge part of being a Whirly-Bird flyer.

Yup! I have found this to be true. its not the host, it is the first one to use the embarking command. I have 8 groups that embark to hueys, After picking up any group with any of 4 helicopters, embarking menu (F7) is still there, but when pressed it only gives F11 and F12 options.

Embarking is working fine, it is a matter of setting a waypoint for the troops (waypoint 1), at the first waypoint, have them embark to transport. Make sure you add any aircraft that they can embark on. Then place waypoint 2 where you want to drop them off. When you land near that waypoint and disembark troops, they will automatically go to the waypoint. Of course, you can add more waypoints after that. but that will do it.

The easier solution is to set a waypoint for the troops then embark from the waypoint, rather than mission start.

OK, I feel like I am the Space Cadet, lol. I wasn't aware that the nav points had to be manually entered. In fact, of the 10K video's I was watching, none of them showed the Rio Entering steer points into the computer. I guess it was a huge assumption on my part to think that if nav points were entered into the mission (via mission editor) that they would be translated to the computer. Feelin pretty dumb, but now I know. The good thing is that after watching all those video's, there is no doubt that I know exactly how to do it! Thanks everyone for your responses. You guys have made me a better rio.

Help! I dont know what I am doing wrong, I have watched 10 thousand videos, read the damned F-14 manual, and still I can not figure out why I can not get the steer points to show on the HSD. If I jump into the Rio seat after Jester has done the startup the HSD shows an arrow to the steer point just fine. If I do the startup, like in the 10 thousand videos, my heading indicator just spins around and around in the compass rose and the HSD does not have a pointer. WHAT am I missing?

I know that we Huey and Mi-8 pilots make up a significantly smaller demographic than the fighter pilots, but seriously, the Huey and Mi-8 Gunners have been BROKEN for FAR TOO LONG! What is the issue? They worked fine for years and years, then you come along with an update that had nothing to do with the helicopters and the gunners cant fire their weapons. HOW HARD COULD THIS POSSIBLY BE TO FIX?