noisy_lightning

I noticed last night that George will not list any search radars for SAM sites. I was targeting a large SAM cluster last night and the search radar would have been a humans CPGs first target to take out the threat, but George was just blind to it. I got lucky and took out a AAA target right next to the radar and the splash damage did enough to stop the radar.

Lamps.lua has all the ones I was after and its now up and running how I expected.

Make sure NVS is turned off, then used Sight Select to switch to TADS.

Hello all, not sure where this belongs so posting in here as its the best place I can tell at the moment. I am running a VPC LED Tool on my machine, which grabs certain exported arguments and allows me to set triggers and LED states based on certain events in cockpit. For example, A/S turns my stick LED green/red depending on safe/armed, I have also programmed my Master Caution reset button to flash when its triggered and then return to green when reset. The way VPC LED works is that there it has the standard telemetry available for every DCS module, that it looks for. Then a second module dependant LUA file for each aircraft specific data. In this case the AH64 has Master Caution as I mentioned above, but not Master Warning. There are a few others missing which I would like as well like Tail Wheel lock. How/Where do I find the list of all exported cockpit arguments for the AH64 please, so I can add them to the LUA to programme the LEDS from Thanks

Thanks, been looking for a replacement for my old out of date reference chart! And having not flown the A10C-II much recently coming back to changed Coolie commands for HMCS and the CMS updatesI was a touch confused last night.

This just went live so thought I would post for you all to see.

Funnily enough I noticed whilst flying on the Hoggit server last night that my 120s seemed short legged compared to how I remember them (been playing the A10 II a lot recently). So it may be a recent thing with the new 120 flight model etc? For context, I was hot, nose on with 2x SU27, TWS, fired on the closest one at 14nm, notched about 20 degrees, switched target and fired on the second one no more than ten seconds later at about 11/12nm, notched a slight bit more till the missiles were both pitbull then turned cold. Both showed lost, and when checking on them in F7 they had both bled out of energy a mile or so short and had given up. The Su27 both remained HOT the entire time, and we had a closing speed at launch ~1000-1200kts. There is no way based on the parameters above they should have fell short...

The same bug is on the A10C 2 as well. Hopefully sorted soon but like Ziptie said, just quickly SSS right/left to the FLIR and bump the TDC.

You're welcome. Took me ages to find it in flight, only got it by accident!

Red is the cross road. Blue is the building you are looking for. Orange is to the jetty with the ships. To help orientate you the solo top right in the FLIR is between the building and the jetty.

This happens to me whether in R1 campaign or not. Turn the tacan on and off again and it sorts it out.

Thank you, that solved it. For my own development, what does stage refer to? For some reason all my kills are not logged either. Would the stage issue affect that?

Hello all, I have finished M08 just now, but when I go to continue the next mission is M02. I have edited the logbook entry to start the next on M09 but no luck, as DCS keeps amending the logbook back to M02....... I have included the logbook lua below incase anyone can help. Its lifted right from the .lua and yes I know that entry [10] says M02. [9] = { ["created"] = "Mon Aug 24 19:32:19 2020", ["player"] = "Dave", ["campaign"] = "./Mods/campaigns/FA-18C Raven One/Raven One.cmp", ["status"] = "Active", ["history"] = { [7] = { ["datetime"] = "Mon Sep 21 20:22:25 2020", ["agKills"] = 0, ["aaKills"] = 0, ["stage"] = 6, ["deathsCount"] = 0, ["result"] = 100, ["mission"] = "R1 M06.miz", }, -- end of [7] [1] = { ["datetime"] = "Mon Aug 24 20:35:19 2020", ["agKills"] = 0, ["aaKills"] = 0, ["stage"] = 1, ["deathsCount"] = 0, ["result"] = 70, ["mission"] = "R1 M01.miz", }, -- end of [1] [2] = { ["datetime"] = "Mon Aug 24 21:46:59 2020", ["agKills"] = 0, ["aaKills"] = 0, ["stage"] = 2, ["deathsCount"] = 0, ["result"] = 50, ["mission"] = "R1 M02.miz", }, -- end of [2] [4] = { ["datetime"] = "Tue Sep 1 21:50:10 2020", ["agKills"] = 0, ["aaKills"] = 0, ["result"] = 90, ["deathsCount"] = 0, ["stage"] = 3, ["mission"] = "R1 M03.miz", }, -- end of [4] [8] = { ["datetime"] = "Mon Sep 28 20:01:47 2020", ["agKills"] = 0, ["aaKills"] = 0, ["stage"] = 2, ["deathsCount"] = 0, ["result"] = 100, ["mission"] = "R1 M07.miz", }, -- end of [8] [9] = { ["datetime"] = "Mon Sep 28 21:25:38 2020", ["agKills"] = 0, ["aaKills"] = 0, ["result"] = 100, ["deathsCount"] = 0, ["stage"] = 1, ["mission"] = "R1 M08.miz", }, -- end of [9] [5] = { ["datetime"] = "Mon Sep 7 21:00:13 2020", ["agKills"] = 0, ["aaKills"] = 0, ["stage"] = 4, ["deathsCount"] = 0, ["result"] = 100, ["mission"] = "R1 M04.miz", }, -- end of [5] [10] = { ["stage"] = 2, ["mission"] = "R1 M02.miz", }, -- end of [10] [3] = { ["datetime"] = "Thu Aug 27 21:01:47 2020", ["agKills"] = 0, ["aaKills"] = 0, ["stage"] = 2, ["deathsCount"] = 0, ["result"] = 80, ["mission"] = "R1 M02.miz", }, -- end of [3] [6] = { ["datetime"] = "Thu Sep 10 20:33:51 2020", ["agKills"] = 0, ["aaKills"] = 0, ["result"] = 100, ["deathsCount"] = 0, ["stage"] = 5, ["mission"] = "R1 M05.miz", }, -- end of [6] }, -- end of ["history"] }, -- end of [9]

I am rubbish at visualising stuff like this so I program a WP into the HSI and then use the CRS and set it to what I am told for the attack run direction. Not sure if you can set a CRS on a Mark Point now we have them? If so that would make it easier, drop a MKPT on the vehicle then set the CRS.

I believe the mission cards are also in the kneeboard which are able to be shown in game and work with VR. Flip through the pages and you will find them.

My suggestion is to print the mission documentation (use the kneeboard if you don't have a printer) for each mission. On there flight plan table there are codewords for each WP. ROCK is the constant codeword for Bullseye (AA W/P) In later missions the mission briefing documentation will be useful for Freq codewords too!

It's a nice idea this. I may adapt it into my HOTAS software as a macro for the same thing, but a single press of a throttle button.

You can't delete them. You can flip the CDU back to mission though on the dial and then only the most recent mkpt will display.

Transfer the key over to the stand alone like I did and it will then show in your eshop account. You will need to move to the standalone version (non steam) but there are only benefits to that anyway!

JSOW is also affected the same way. Had to align them multiple times two nights ago.

You need to get closer. It will deploy when you are close enough. Approach tha tanker just below it and when not much away from the refuelling distance report ready pre-contract again, it will work.

I think the OP meant it doesn't have them in dcs at the moment. Rather than at all in RL. Mark Points is by far the biggest thing I want added to the F18 at the moment to improve cockpit work flow. I flew the A10c recently again and it's so much better, I know it has a different design philosophy but even with the F18 systems, mark points will be a huge improvement in quality of life!

Assuming you have the TGP on the right DDI, SSS right once to set the right DDI as SOI. Double press the nws/undesignate button to switch to VVCL mode and then double press again to put it into snow plough mode. You can then from snow plough mode slew again. I think that this is a bug, well at least I hope so as I have found this issue a few times. An alternative method is to cycle the tracking mode (INR/ATRK/PTRK) Using SSS right, once you have the yard stick back on the screen it should be slewable. This method doesn't always work for me though and I have to use the method above.

I had the same with a dodgy (old) unpowered USB hub. Replaced the hub and all was well again. If you are not using a hub then try switching the USB sockets anyway. Could be a windows device allocation issue.

Sounds like a metashader issue and/or maybe a graphic card driver issue at a push?