Amarok_73

On the other side, since about last two updates I noticed increased number of CTDs related to the D3D11.dll file, where prior to the CTD there's number of messages like "DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED". But, that's another story, and each error log package I am sending, so staying within the subject of this thread, seems indeed like we can celebrate...

Tried all my tricks to pull it from the box with surprises, but no - it's gone.

Impressive. i can imagine such scenario with planes like Tornado or others that are capable to set and show the planned TOT (Time Over Target), but if the HB implementation of Viggen is accurate, having in minds what I've learnt so far about this machine, to arrange and execute such a mission had to be hell of work. And money required to train these pilots. I hope that I'll master one day this plane enough to say I am able to participate in such mission, but so far I am going back to Chuck's documentation and YT movies. As I've just bought this plane and there's a lot of training in front of me.

That's what I supposed besides of that I am doing something not according to the procedures. Thank You for confirmation, and help at all! EDIT: I found the reason. It was just the rotary assigned to MKR/Radar Gain function set to minimal value. Totally forgot about this one.

And what about the radar not returning any picture? On the screenshot I have highlighted out of the window and on the kneepad that I am right next to the Cyprus coast, but radar returns nothing...

This is also my observation so far

@Rudel_chwThank You for response. Yes, I already noticed that this plane is enough as opponent for the Mig-21 and other planes from this era, so I am focused now on the ground/sea capabilities. Just about now I've finally successfully attacked big-ass tanker with RBS-15F missiles (weeee!), sadly such attack seems to be rather not possible against armed fleet, as all my missiles so far was downed by escort ships.

Yep, it works as You guys described. Another questions: 1. Why sometimes after start, when I'll enable radar it returns nothing, regardless of the elevation I set with rotary? Seems like i enable it in wrong sequence...? 2. Is there any visual indicator showing the current radar scan elevation? According to the Chuck's manual there should be something on the top of the radar display, but I can't see anything there. Here's screenshot from the Chuck's manual where it is shown: 3. Sorry to ask this one, but I have problem to find the answer on it in the documentation : near the elevation rotary limits minimal and maxima, the radar sweep starts to be quicker and narrower and when rotary is at the top value it stops sweeping at all. Are these some special radar modes?

Ok, I'll give it a try. Thanks for hint.

Hello, I'd like to ask if it is me doing something wrong, or it is impossible to enter into the navigatioin computer coordinates higher (longer) than 99 degrees? If so, is there any other reliable method for it independent of the points (pre)entered in the mission editor?

+1

Looking forward to put my hands on it and break it

... that elevation limits visible on the left of TID shows actually the values for the place where the TID cursor is located. XD Never before I've looked at these when was messing with cursor around, and for some reason I overlooked it in all manuals/turorial videos I've seen so far (if it was mentioned in any of these). Oh man, what a relief...!

Yes, the same here. Couldn't be easier to reproduce

Try to disable ATOC in graphic options, and You'll see the magic. And regarding the question about the newest drivers, I've installed them, and issue is still there.. .

Hello, I'd like to ask if there's any way to reset/reload/end mission with LUA only, without using the trigger that will do this action? The action itself would be triggered by evend of deleting the mark from the map having specific text in label like "reboot". So far I know how to set the flag with it that will trigger the action defined in the triggers, but I'd like to do it with the LUA code only.

Hello, I have such a script, where I'd like to add the entries for carrier based squadron: function fGCICAPBlue() env.info(">>>> Blue GCICAP starting...") BlueDetectionSetGroup = SET_GROUP:New() :FilterPrefixes({"BLUE EWR", "AWACS Blue", "BEWR"}) :FilterStart() BlueDetection = DETECTION_AREAS:New(BlueDetectionSetGroup, 30000) BlueBorderZone = ZONE_POLYGON:New("Blue Border", GROUP:FindByName("BlueBorder")) BlueCAPZone001 = ZONE_POLYGON:New("Blue CAP Zone 001", GROUP:FindByName("BlueCAPZone001")) BlueCAPZone002 = ZONE_POLYGON:New("Blue CAP Zone 002", GROUP:FindByName("BlueCAPZone002")) BlueCAPZone003 = ZONE_POLYGON:New("Blue CAP Zone 003", GROUP:FindByName("BlueCAPZone003")) --BlueCAPZone004 = ZONE_POLYGON:New("Blue CAP Zone 004", GROUP:FindByName("BlueCAPZone004")) BlueA2ADispatcher = AI_A2A_DISPATCHER:New( BlueDetection ) :SetBorderZone(BlueBorderZone) :SetDefaultGrouping(2) :SetEngageRadius(200000) :SetDisengageRadius(150000) :SetTacticalDisplay(false) :SetDefaultTakeoffFromParkingHot() :SetDefaultLandingAtEngineShutdown() :SetDefaultFuelThreshold(0.30) :SetDefaultDamageThreshold(0.40) :SetIntercept(450) BlueA2ADispatcher:SetSquadron( "Fujairah", AIRBASE.PersianGulf.Fujairah_Intl, { "BlueGCICAP01" } ) BlueA2ADispatcher:SetSquadron( "Sharjah", AIRBASE.PersianGulf.Sharjah_Intl, { "BlueGCICAP02" } ) BlueA2ADispatcher:SetSquadron( "Khasab", AIRBASE.PersianGulf.Khasab, { "BlueGCICAP03" } ) BlueA2ADispatcher:SetSquadronGci( "Fujairah", 600, 1200 ) BlueA2ADispatcher:SetSquadronGci( "Sharjah", 600, 1200 ) BlueA2ADispatcher:SetSquadronGci( "Khasab", 600, 1200 ) BlueA2ADispatcher:SetSquadronCap("Fujairah", BlueCAPZone001, 3000, 10000, 500, 800, 500, 1200, "BARO") BlueA2ADispatcher:SetSquadronCap("Sharjah", BlueCAPZone002, 3000, 10000, 500, 800, 500, 1200, "BARO") BlueA2ADispatcher:SetSquadronCap("Khasab", BlueCAPZone003, 3000, 10000, 500, 800, 500, 1200, "BARO") BlueA2ADispatcher:SetSquadronTakeoffFromParkingHot("Fujairah") BlueA2ADispatcher:SetSquadronTakeoffFromParkingHot("Sharjah") BlueA2ADispatcher:SetSquadronTakeoffFromParkingHot("Khasab") BlueA2ADispatcher:SetSquadronTanker("Fujairah", "TKR130") BlueA2ADispatcher:SetSquadronTanker("Sharjah", "TKR135") -- BlueA2ADispatcher:SetSquadronVisible("Fujairah") -- BlueA2ADispatcher:SetSquadronVisible("Sharjah") -- BlueA2ADispatcher:SetSquadronVisible("Khasab") --BlueA2ADispatcher:Start() env.info(">>>> Blue GCICAP started.") end fGCICAPBlue() Can anyone tell me, how it should looks like to make it possible? On carrier I've two groups, single unit each, both late activated that I'd like to have as the Fleet Defenders that will depart as soon as the Dispatcher will decide that there's enemy that should be redirected back to where it came from.

Sorry to bring the bad news, but it's still in place with this drivers version...

Unfortunately it's not true. Use of this button speeds up the issue, but without using it, eventually the bug will happen anyway.

On the screen these buttons looks the same and the red cockpit light is blinking.

Against you and your little crusade? None. Let's treat it as the "WZL 1" modification: https://www.digitalcombatsimulator.com/en/files/3317035/

https://wzl1.mil.pl/helicopter-upgrades/ ... and the last position from the list.

I can see, that the easiest way to trigger this issue is to choose mission on the Marianas Islands. Can anyone confirm my feelings?

Here are the track file, log file and the screenshot from GLOGG showing the line that was active when the bug have happened. Graphic bug with log file.trk dcs.log

I wasn't aware of this option(s), so I've checked it and apparently, I've had them all the time disabled. By curiosity tried to enable it, and all my devices was messed-up. HOTAS was not discovered by system, keyboard had non-functional keys like spaces...