Vakarian

Afaik, Harrier is not supported by Supercarrier module and by extension SC ATC. Hopefully it will get sorted out "soon"

Also cannot reproduce. Downloaded your miz file, pressed DESG about 10 times, all works fine

Thanks for the update :)

In my sqn we have found the issue where on CVN-75 we cannot align INS. We had 6 birds, none has managed to go past "40" counter on the INS. All we get is that box instead of chevron marking the current alignment status and it won't continue no matter what we do. So far, we have tried to do some tests and it seems that CVN-75 is missing the datalink. On CVN-71, 72 and 73 of the Supercarriers and on CVN-70 and 74 of the old carriers there is datalink and the alignment completes normally. Only the 75 seems to be the issue. Datalink is not showing on the kneeboard and there is no datalink found on the Jester menu. As I'm not sure if this is HB or ED problem, could you take a look at this and see what can be done?

Oh yeah, these sounds.... I wouldn't mind in just ripping the sound from this video and jamming it in the sim. Really sounds awesome. Also, If I saw correctly it has 408 engine, same as we have in the sim so it is a relevant video in showing the engine performance and also, some HUD things. Mainly, I noticed that there's a "W" flashing when he goes over 100% RPM, but I'm not sure if that means no water intake is enabled or that it is enabled (W lighting up on the engine panel is not shown clearly)

Just stumbled on an interesting video on YT. Here, from idle to max RPM it took him about 6.5 seconds, and nearly the same from max to idle (no HUD or engine page showing, so I was going by the amount of whine)

You mean something like this: https://forums.eagle.ru/showthread.php?t=269108 To be honest, couple of bug from there are fixed, but only a couple. A LOT are still not, so it's kinda disturbing.

I've started doing a little project to improve my coding skills, so I thought of doing a Logbook which could track my SP and MP sessions. I quickly stumbled on a problem because in debrief.log, after a MP session I cannot see my Callsign to discern which initiatorMissionID is mine and to track events by that ID. Also, every single client gets it's callsign as "New Callsign" so something is wrong there. After SP session it works correctly. Only workaround I've been able to figure out so far is to parse dcs.log simultaneously and look for a "DCS: MissionSpawn:spawnLocalPlayer 311,AV8BNA" line. That line says that my initiatorMissionID is 311, but the problem is that dcs.log doesn't refresh after each MP or SP session as it tracks everything from when DCS is started until DCS is finished running. That means I'll have multiple lines that I'll need to crosscheck with the timestamps to match certain ID from dcs.log with the actual debrief.log initiatorMissionID. My question is can this be looked upon so that each client gets it's Callsign properly written inside debrief.log?

#4453 is on it's way, hopefully it'll reach me soon. Can't wait to replace it EDIT: Installed it today and I'm loving it. So much smoother and easier input.

Just wanted to be sure, but there's nothing stopping me from buying some FSM-DIY kits, and use them to create multiple panels for my simpit?

For me it's exactly the opposite. If I grab and spin, it goes to max and stops there. Using the mouse scroll lets me turn it around from max to min

Well, you are definitely doing something wrong, the issue is what. Laser must be armed, and in "LASR" mode, marker and traing modes are not for weapon employment. When in "LASR" mode, FIRE should be underlined. Also, slant range needs to be under 8nm, so make sure you are close. You didn't mention but I assume you are using CCRP delivery? If so, you shouldn't have any issues hitting your targets if you do all of the above.

When I learned of the advice to delete metashaders and clean fxo folder after every update, I haven't noticed any drops of performance and if anything, helped to have stable performance after pretty much every update. To be clear, speaking of (C:\Users\XXXX\Saved Games\DCS.openbeta\metashaders2, C:\Users\XXXX\Saved Games\DCS.openbeta\fxo, D:\Eagle Dynamics\DCS World OpenBeta\Mods\terrains\FOR_EVERY_TERRAIN\misc\metacache\dcs and D:\Eagle Dynamics\DCS World OpenBeta\Mods\terrains\FOR_EVERY_TERRAIN\misc\shadercache) Only downside of this is everytime after an update, every terrain and game loading takes a little longer, but if that helps to prevent potential issues, I think it's an option everyone would prefer. What I'd like to suggest it to implement clearing of these folders to the DCS updater application, so after every update they get automatically cleaned during the update without players having to worry about that. I bet there are a lot of players unaware of this and they could have issues because of having older shaders installed so having this clearing automated could help a lot. Is it possible to forward this to the devs to take a look at? Regards, Vakarian

I mean, even in 2D they aren't really optimal so some adjustments are necessary. If they could make it as an option with some sliders adjusting thickness and the scale, that would be the perfect solution. Even more now that they implemented custom graphics presets so we can save one preset for 2D and one for VR

First of all, sorry if I placed this in the wrong section. I noticed some pretty frustrating issue while doing any tutorial mission (screenshot are from Ka-50 because of free trial :thumbup: ). When tutorial ask you to flip a certain switch(es) it marks it with a helper box. That's all fine and great but in VR that helper marker is way too big. I have tried using the VR zoom, but that doesn't help at all. Now, I know that it's centered on a switch I need to press, but it becomes a mess when you have multiple switches in close proximity and the mission marks them all (see screenshot HowItIsCurrently.png). I'd like to ask for a possibility that those markers get smaller or at least some option for every player to set it's own scale of those markers. See screenshot (HowItShouldBe.png). While doing that startup mission, it took me around 3 minutes to figure out what does the marker mark as it was my first time in the Ka-50 cockpit and I had really no idea what does any switch mean. Also, it wouldn't hurt to adjust those markers in the 2D version as well. What immediately comes to mind is the A-10C startup sequence where the boost pump switches are marked. With that amount of markers, they quickly become a clutter that masks the switches. Regards, Vakarian

When creating mission, I made 2 tankers, one one TACAN 10Y, other on 11Y. However, when I started the mission, went to find the tankers and on Y band I'm not getting any response. When I switched to X band, I found both tankers. On Discord's bug section I had asked the same question and I got a response that Airborne TACANs created on Y band using mission editor will revert to X band, while only using MOOSE scripts Airborne TACANs stay on Y band when created as such. Could this be looked into? It's very easily reproducible. Thanks in advance. EDIT: I added the mission file and track to ease the report process. airborneTacanBug.trk airborneTacanBug.miz