-
Posts
125 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Olddog
-
-
With the APC Sd.Kfz 251 in a mission every time it shoots, I get this in the log file: 2020-06-24 13:18:47.069 ERROR DCS: Can't find score constants for 7_92x57_Smkl 2020-06-24 13:18:47.069 ERROR DCS: Can't find score constants for 7_92x57s Repeating 100's of times, the above two entries for each shot.
-
Yeah same thing here, they were working great but after that last hot fix they stop launching.
-
Ok here is my last debrief.log This was a P-47 on the Channel Map. The enemy part was just me trying out different enemy selections to see if it made a difference. debrief.log
-
-
I "think" the Attack Group & Attack Unit will only work for Fixed wing and helicopter groups. From the DCS manual 2020, page 218 Attack Group Attack a specific enemy air, ground or naval group as designated by the mission designer. Applicable to: Group type(s): fixed-wing and helicopter groups;
-
You could give this script a try and see if it will do what you are wanting. https://forums.eagle.ru/showthread.php?t=187181&highlight=smart+ia
-
I would like to see the single key bind for ALL the red guards/switches
-
This is working on the Channel Map and OB. https://forums.eagle.ru/showthread.php?t=192550&highlight=chain
-
DCS-ExportScripts P-47D Thunderbolt .lua script
Olddog replied to nosaMtrevoC's topic in PC Hardware and Related Software
I have a work around for the ID lookup until the plugin gets updated, if you want to mess with it. This is what I did. Go to C:\Users\YOURNAME\AppData\Roaming\Elgato\StreamDeck\Plugins\com.ctytler.dcs.sdPlugin\propertyinspector\json Open the file, cached_commands.js, with something like notepad ++ (make a backup copy of course ) I don't own the Yak52, so I searched for "Yak52:" which was down near the bottom of the file. Or search for a module that you don't own. If you own all of then, pick your least favorite.:smilewink: I replaced "Yak52:" with "P-47D-30": I made no other changes. Hopefully ctytler will get around to an update to add in the P-47 to his great plugin. Note: Under the ID lookup Description list, the reference to things like Yak52,xxx Spitfire xxx,and even BF109 xxx is from what is in the P-47 clickabledata.lua file. I guess someone did a lot of copy and paste:smilewink: -
DCS-ExportScripts P-47D Thunderbolt .lua script
Olddog replied to nosaMtrevoC's topic in PC Hardware and Related Software
I think it's more or a label thing. For example , your [139] = "%d",-- LH Wing Bomb Switch Should be .. [139] = "%d", -- LH Wing Bomb Cover, (Red guard) The actual bomb arm switch is [140] ="%d", -- LH Wing Bomb Switch Is what I was trying to say. -
Some interesting facts. Seven of the top 10 European Aces flew the P-47 Thunderbolt against the Luftwaffe. Thunderbolt’s knocked 3,752 enemy aircraft out of the air while destroying another 2,800+ on the ground. The heavily armored plane sustained 824 combat losses, only .07% of the Jugs didn't return from a combat mission, the lowest total of any Allied fighter. The Thunderbolt flew twice as many sorties and dropped 2,010% more tonnage than any other Allied fighter. http://www.368thfightergroup.com/index.html
-
DCS-ExportScripts P-47D Thunderbolt .lua script
Olddog replied to nosaMtrevoC's topic in PC Hardware and Related Software
You might need to check your Drop Ordinance Arming Panel IDs. The Red guards(covers) have to be up before the switch will work. It would be nice if we had a way to toggle the Red Guard and switch ON at the same time without having to use the SD multi-action. This is what I have. [139] = "%d", -- LH Wing Bomb Cover [140] = "%d", -- LH Wing Bomb Switch [141] = "%d", --RT Wing Bomb Cover [142] = "%d", --RT Wing Bomb Switch [143] = "%d", -- Belly Bomb Cover [144] = "%d", -- Belly Bomb Switch [145] = "%d", -- Left Chem Cover [146] = "%d", -- Left Chem Switch [147] = "%d", -- Right Chem Cover [148] = "%d", -- Right Chem Switch -
See here about the Schnellboat. https://forums.eagle.ru/showthread.php?t=274539&highlight=Schnellboot
-
-
I tried a similar setup, P47, Normandy, FAC, Tanks. all I can get is " No further tasking available "With the FAC on unarmed trucks , everything thing works fine. So maybe just a vehicle type issue.
-
For Paratroopers.. this mod still works with Channel Map, Normandy and OB 2.5.6.50321 https://forums.eagle.ru/showthread.php?t=222914&highlight=dc3
-
P-47D ID Lookup I made a simple 3 item export file for P-47 to use for testing,and when checking it with DCS comms, the values will change. That part is good. But the ID Lookup shows nothing. Now for the weird part. Thinking maybe that the DCS plugin didn't like the double "-" as in P-47D-30, I renamed the Dir to P-47D,.nope that didn't work. So on a whim I made a backup copy of my TF-51D Dir, coped all the P-47D-30 stuff to the TF-51 and I'll be .. ID lookup showed all the P-47 items. Of course I can't fly it this way, so I put everything back the way it was supposed to be. My question is how do I get the plugin to recognize the P-47D-30, without all the tricks ? Thanks
-
The LCD showed up showed up at night,which I didn't think off trying. Thanks Looney
-
Is there some secret to get the red lcds to work on the UV-26? The left/both/right indicator LEDs work, and flares will fire but the 3 red LCDs are blank. This is with default cockpit or English cockpit. OB 2.5.6.47404
-
Lua scripting : monitoring static object status ?
Olddog replied to CougarFFW04's topic in Mission Editor
Thanks Hardcard, I appreciate your help , that script works just fine and it is a plus that the static names don't have to be changed. -
Lua scripting : monitoring static object status ?
Olddog replied to CougarFFW04's topic in Mission Editor
Hardcard, First, I hope you get over the Flu soon, that can really suck. This is your .miz with Mist added and nothing else. You will get the first 4 or 5 destroyed messages and then no more messages when the rest of the static targets are destroyed. When you get time, give it a run through and see what you think. The first targets are destroyed at the exact same time so the OnEvent message is triggered once, and then seems to just quit. Just for the heck of it I separated the targets on the runway with more room between them and only got two destroyed messages.(both at the same time) In all cases, all the targets were destroyed, just didn't get the messages. Again this only happens when Mist is loaded, with just Moose everything is as advertised. I'm using Mist for all the other usual stuff and is the only reason I brought this up. The info from your script would be nice to have. OnEventDead Static Test v3 (corrected)_mist.miz -
Lua scripting : monitoring static object status ?
Olddog replied to CougarFFW04's topic in Mission Editor
Hardcard, I was trying out your OnEventDead scrip and it all works fine, and thanks for sharing. But (always a but) if Mist is loaded it doesn't want to play well. I was going to use your script it in one of my missions but I couldn't get it to work. So I went back to your demo miz from above and added a new MISSION START -> load Mist (4.3.74) and changed nothing else and then ran you mission, (just to make sure it wasn't something I was doing in my mission) I would get the "dead message" for the first 4 targets and then nothing.The debriefing shows about 20 dead targets Take Mist out and everything back to normal. I would almost swear I have used Mist and Moose together before with out any problems. This is on the latest OB. Is there something else I could try ? -
This works also. CombatFlite has added the ALE-47 programer https://forums.eagle.ru/showthread.php?p=3747812&highlight=ale-47#post3747812
-
[REPORTED] Cannot re-arm F-18 at Al Dhafra AB on Persian Gulf
Olddog replied to HC_Official's topic in Bugs and Problems
Ok I understand what you mean now. For the individual stations, I can not select a new weapon. It's like the menu is not opening up to the right. I am able to select a new load out from the "Select Loadout" drop down menu. So I would agree that something is not working correctly