zerO_crash

+1

In the following video: at 1:15 you can see snap-shot of the radar display. First thing I notice is that the radar has a 160 km range setting. We got 120 km. Is this possibly a different upgrade/version of the viggen? Additionally, I notice that the image at 160 km is very crisp in fidelity even at such long range. Comparing to our AJS, where the picture starts to blur from right over 70-80 km range. How come? Thx for the module so far Heatblur, you guys are doing great. :thumbup:

Fixed sight (code 211) worked for me in two missions. The rest of those I flew, upon inputting the code and readying ARAK, I get a blank HUD. I know this was reported before, but back then it didn`t work at all, now however it works inconsistently. Hope you can fix it soon, ARAK seems currently to be unusable due to problems with both fixed and calculated sights.

After passing a certain altitude (somewhere between 1000-1400m ASL) the HÖJD CISI switch automatically switches to LD if it was set to RHM prior to passing that altitude. It`s also unable to switch it manually back to RHM unless one goes down in altitude. Is this correct working? Cannot find nothing mentioned about this in the manual.

Not sure why, but when ARAK rockets are selected and ready for fire, closing in on the ground will in some cases make the sight jump around preventing any accurate impact determination. I`ve checked that I`m within parameters for ARAK employment as per manual. EDIT: Meant ARAK, disregard thread title "akan". After testing some more now, I noticed that after setting "SLAV SI" to "Från", it jumped around less, but still enough as to make it inaccurate.

Seems the problem was fixed for me by updating to the newest graphics driver. (Was Nvidia) Mod, lock the thread please.

Apparently, after flying gazelle today, twice has my system frozen. It happens after I fire a missile, right before it impacts the target. I have no problems with any other modules, no crashing, no freezing, etc... It happens randomly, once after firing first missile, now after firing 8th (after rearming). But gazelle however does. Check attached logs folder. - No mods, DCS 1.5.6 Final (latest update) - I7 3770, Nvidia 780, 16GB GDDR3 RAM... - Windows 8.1 Professional DCS-Crash-20170225-161636.zip

Well guess that explains then. Just weird it wouldn`t handle different on equal opposite pylons, but it does so with different pylon-pairs. Thanks for responses :thumbup:

Works without any problems here. Are you warming the radar up?

Is there a reason why uneven loadout is prohibited? Noticed recently that when I tried to load a Super 530D on one side and take two mk82`s on the other (opposite equal pylon), only one of the two would get rearmed. I am fully aware of the A-G mix restriction, but uneven loadout? I also noticed some time ago that I cannot choose whether I want my A-G on the rear wing root pylons or front, apparently it won`t let you add weapons to the rear pylons unless the front wing root ones are occupied first. What`s up with that?

Belly, you willing to fix this soon? Pretty please with sugar on top? No?

Thanks much :thumbup: I might have figured it right now, went ahead and took off. Went then into controls and unbound my rudder. It didn`t happen anymore. This would point at the default rudder needing a little bit of dead zone possibly? I cannot do much with FFB and curves. Would it be fair to say that dead zone need an increase considering other modules aren`t sensitive to wind blows on the pedals?

Is this issue being looked into at all, or? Kind of hard to decide what to do with 0 input from LN... Do you need more tracks, or some other proof or?

"Weapon not being usable after rearm fixed." Does it refer to Mavericks? Hope so :pilotfly: Also, Cobra, would it be possible to add a Master Arm/Trigger Safety (on stick) toggle switch? Would prefer that over two separate keys for on and off. Great going so far :thumbup:

Funny enough, it could be the case, as I usually fly right at the waypoints.

Well, I have never had problems with curves, and with my MSFFB2 it`s pointless to add curves. I just hope they manage to fix this soon. But thanks for your suggestion :)

It`s fair if they want to start laxing on things, but make it under game option or special. If we start laxing things now, just to suit the bigger audience, it will be a irreversible effect which will in the long run make DCS ace combat. I`m sure there are ways to implement it to not harm the module in a SIMULATOR in any degree.

Also, just did more testing, and indeed the plane is living its own life. After a sortie now, upon extracting landing gear and lining up on final, I again noticed a series of small departures from my heading, this time I looked at the pedals, and noticed that with absolutely no input of mine, and pedals in the middle, the rudder pedals in the plane were moving when these departures happened. Having flown all day Mirage yesterday, now I am certain it must be something with the SPAK. Could it be that the aircraft engages rudder automatically when rolling over a certain degree? Does it maybe account for wind and tries to adjust? RagnarDa, or anyone from LN care to elaborate? Notice in the track, when I get back to base, and just before landing. I did not use any rudder at some 4-5 min before landing, but I`m sure you can see that from inputs. Notice how the aircraft does it`s magic with the rudder. EDIT: Flew again a different mission, this time even worse. Rudder kept working while cruising around, and no input of mine was given. server-20170205-110121.zip

Yes noticed that too. Done with 2x RB05 + 1 AKAN + 1 KB.

Never had such a problem before, nor do I currently have. I seriously doubt it`s anything on my side. I have rebound the rudder axis and done a recalibration, and to no avail.

I notice it. I fly straight, and suddenly the plane get`s pushed into a medium roll and with nose off course. Basically, same as flying straight and giving medium rudder or so, specifically with this plane.

Here you go my good sir. :) dcs.zip

There are two things I noticed with SPAK: - Flying straight or turning, the plane will pushed off course heavily, as if rudder pedals were pushed, even though they are not. I usually fly with windy conditions, but tried even without and no turbulence too. Same problem. Again, it happens sometimes, fairly often. Must be a problem. - This I am not sure of, but even with the newest patch, giving the plane even tiniest rudder input makes it want to roll and go instable very rapidly. Now I`m not inferring that this is incorrect behavior, but compared to the other planes we got in DCS, it`s rather heavy. Is it supposed to be that pronounced? Tried both above and below 350km/h.

After longer missions, upon shutting aircraft down, changing the mode selector from "NAV" to "BER" causes a DCS crash (stopped working). Track attached. server-20170203-155935.zip

How would you know about the locking time? There is nothing in the mentioned tests on what they were actually testing. A pilot is taught to prepare himself as early as possible for an interdiction, that gives him more time and offloads him when he needs to make the decision whether to pull the trigger or not. If this was a simulation of the weapons effectiveness in a real scenario, one could imagine the same tactic being used as was used with the A10A, where the maverick sensor was used as a means to identify a target through the Maverick optics. In which case locking on early would be the preferred option. Again, let`s not extrapolate things that are clearly insufficiently described through a couple of diagrams.