dwpenney

Sorry to necro an old thread. Ranger, did you get it working for more than 1 radio transmission? I have a mission where I get only the first, followed by continuous static ... until the second is triggered. When the second is triggered, the static stops but I do not hear the second transmission. No transmissions after that seem to do anything. This is all from the same zone, same frequency, power, everything ... except different ogg files on DCS World 2 OpenAlpha. Anyone else getting this?

I am late to the party here but I have been looking at MOOSE over the past two months and thinking that this could build into something really significant and something really useful. As with most DCS Mission Editing, it is a serious up-hill battle in a quiet part of the forum. It takes time to generate momentum but the design and implementation of this tool set looks very promising. I am sad to read that it may be abandoned. I realize that it is a lot of work and hearth and family obviously come first. I hope to see you back here again someday and I appreciate the hard work you put in to this.

I made a mistake last night where I entered the position of my aircraft incorrectly during the INS warm up. When entering the Lat/Lon coordinates of my aircraft I entered E instead of W (W being where nevada is and I was used to entering E, where Georgia is). That lead me to an instance of being 90ish degrees off. So, one tick on the INS Align dial to VEI, enter +N ###### when +E ###### when it should have been +W ###### EDIT: Correcting my post: It was the HSI mode that ad me off. NAV had be off 90+ degrees whereas Cm/Cv were fine.

Donated!

I am interested!

Looking forward to it!

I was wondering about this. I noticed it in the Sabre last night and could not remember the steering being as difficult as I was experiencing. This explains it ... I think :-). We we found (flying online last night) is that the steering would get stuck in a direction and would not un-stick. In my case, I ended up with a drift to the left and no amount of right rudder, with the steering button engaged, would correct it. If I understand correctly, I would have had to put some left rudder in, to get the mechanism and nose wheel to latch, and then I would have been able to steer right (and not off the runway and/or taxiway). Do I have that right?

It did for me. When I hit RALT+Enter and started a recording, it went into the Digital Combat Simulator Black Shark folder instead of the Desktop folder.

Leave it with me. I will take a look at replicating it in a more reliable fashion.

It was causing an issue yesterday with version 1.5.0.45208 on both the client and the server. In the .zip file, if I uploaded version 07b of the mission, the crash would occur. I removed the Ha-27's in version 07c of the mission (also in the zip file) and the problem did not occur. In 07b I have 1 Ka-27 of the USAF Aggressors flying along with the carrier group. This would cause a crash on any client that attempted to connect to the server running this mission. If the Ka-27 was deleted, clients could connect. EDIT: IT should be noted that if I try the mission on my PC via the mission editor, I do not get a crash. It was only when the mission was on a separate dedicated server.

I am getting the same thing ... but ... it also happens in mission. So, no texture in the encyclopedia but also in game. Which is odd. I tried removing the module and reinstalling, same issue. I also compared the directories for the Ka-50 (mods/aircraft/Ka-50) between the main DCS install and the Open Beta and there are no differences. Attaching my System Info file. Please let me know if there is anything I can do to help debug this. EDIT: Ignore that previous edit (removed). The texture issue in game is related to the US Aggressors faction. That faction has no skins associated with the Ka-50. That may relate to the encyclopedia entry having no default texture like the agressors. system-info.zip

This seems to work on my PC before uploading it to the server but when I connect to the server I get a crash as the 'Select Aircraft' menu/screen. It appears related to the Ka-27 that I had escorting a carrier. I 'copied' the pattern from the Su-33 campaign ... which did not work so I replicated the carrier group and added a couple of Ka-27's as I had seen done in the Su-33 campaign - which I thought was a nice touch. When I take out the Ka-27's, the mission does not crash. I am attaching a zip with the crash logs, system nfo file and the mission with and without the Ka-27's. 2102-crash.zip

Has anyone tried this script in DCS World 1.5? EDIT: Just tried it in the mission editor and it didn't seem to work. Both test groups flew straight and level with no CAP or GCI launching.

I think we ran into that last night. If you are clicking 'open' you are actually opening the mission list file (.lst). There is a plus symbol button there somewhere to add a mission to the current list.

I found that if you click on something in the column for the control, it's name will appear correctly. In other words in the above screenshot, if you clicked on the Thrust entry for Joy_Z (clicked on the Joy_Z cell in the Thrust row) then the label at the top of the column becomes readable (while a cell in that column is selected). That's a work around.

Appreciate the effort. Please announce it when you are ready, not before. :-)

Then I would change my vote from SU-25 to Mirage. I don't think people realized how long it might take. Plus, I don't see this vote as a binding agreement. Mirage is a fine choice.

Thanks Wags!

That's a DCS problem. I think it's been broken since 1.2.8

Some people would still be unhappy. This is a situation where there is no answer that makes everyone happy, just attempts to minimize that pool of potential customers. Think about it an anticipate the response. People would still be upset because then they would have gotten nothing and would be forced to buy the aircraft they had already paid for again. No matter what ED did, there would be unhappiness in the forums. Personally, I appreciate getting something. I don't blame ED and Kickstarter has some risk inherent in it's purpose. I do blame RRG for being unrealistic, chaotic and confused. In the end, there still would have been tears.

I am happy with this. It could be worse, much worse.

I should have some good RCAF Golden Hawks images if they are needed.

That's exactly what I am doing in my script. On an Eject event, spawn a downed pilot (because I can't seem to access the one DCS generates) and set a transponder pinging from that pilots position with the above code.

Example of another cool thing you could potentially do with this: Windsocks

Any chance of a response from ED? I am getting to the point in my code that I either need to take advantage of the opportunities offered by being a module or making more work for mission designers. I will soon have to shelve my ideas for others.