funkyfranky

I would prefer it to be as realistic as possible and restrict the number of rounds, i.e. no unlimited ammo please. On top of that, Simshaker (haptic feedback device) does not work with unlimited ammo as per DCS restrictions (number of bullets does not change).

Even the Russians confirmed it by triangulation. What more can you ask for :D

Indeed and other units like certain helos are affected as well.

Still present in DCS 2.5.5.33552 OB.

LOL, well, looks like I get influenced by people that surround me more than I want to :megalol:

Yeah, but not a good one if you cannot make out important landmarks any more ;) I figured that is is some kind of "optimization" but this should be improved if possible. So I stick with the "bug" tag for now :P (at least in my internal nomenclature).

This! Something changed in the latest version that also makes dynamic spawning impossible until the previous aircraft has taken off (or at least is about to on the CAT). Talking about the Stennis here.

Could not agree more.

DCS 2.5.5.33552

The mountain, in fact a landmark shown in the Bunyap Viggen Red Flag Campain is not completely visible from a distance. You can see that the smoke is floating in the air. Pic was taken in VR with visibility high. When you use the VR zoom, the missing part of the mountain becomes visible.

Any news?

Interesting, but why did you not post your findings on the official request thread?

The wiki is an awesome resource and absolutely vital. But if I am not mistaken, this is a unofficial source. So no guarantee that it is up-to-date or that it even will be supported in the future. The main problem, however, is that there are things "people" simply don't know. So we cannot put this in the wiki even if we wanted to. For example, I have asked about the parameters of the getParking function a couple of times - just recently even in the russian forum part so the devs could maybe enlighten me. Even there, no response at all. While it is nice to have a function like this, it is only worth half the money if some of its functionality remains a mystery.

Yes, would be nice to know. With the provided data, there are only two possible conclusions/scenarios: VR improvements are restricted to a very special combination of hardware and/or settings. Error in measurement of the few outliers who actually saw an improvement (in other words no measurable FPS improvement). I hate to be that negative, but case 2 appears to be far more likely to me given the simplicity and hence error margin of the test and the majority of people with very different hardware and settings who saw no improvement.

Proper and up-to-date documentation. Also and especially for the functionalities available via scripting. See 1. See 1. See 1. Undo function. See 1. See 1. See 1. See 1. See 1.

If it is possible depends on whether this new feature is available via scripting. Unfortunately, nobody really knows as there is no official documentation about any scripting functionality in DCS. Of course, there are very easy and convenient ways to delay a message with MOOSE and (probably) MIST. Also the native DCS API would allow you to schedule the message. If you need help with that, just shoot :)

Yes, noticed that as well. DCS 2.5.5.33184

FW-190A8 Anton Hi Olaf, hope the renovation is going well! I have messed a bit with the ShimShaker.lua file and tried to include the Anton as it is very similar to the Dora. Here is my suggestion: elseif obj.Name == "FW-190A8" then ------------------------------------------------------------------------------------------------------------------------------------------------------- local Manifold_Pressure = MainPanel:get_argument_value(46) -- Same as D9 local Engine_RPM = MainPanel:get_argument_value(47) --Same as D9 local PanelShake="0.00~0.00~0.00" -- No panel shake. local GunFireData = string.format( "%.2f~%.2f~%.2f~%.2f", MainPanel:get_argument_value(50), --MG-151 Left Wing (outer) MainPanel:get_argument_value(164), --MG-131 Left Rumpf MainPanel:get_argument_value(165), --MG-131 Right Rumpf MainPanel:get_argument_value(59) --MG-151 Right Wing (outer) ) local MW = 0 --MainPanel:get_argument_value(106) -- No MW -- FW-190A8 sends to SimShaker as -D9 stringToSend = string.format( "T=%.3f;N=%s;SelfData=%s;EngineRPM=%.2f;VlctVectors=%s;altAgl=%.2f;PanShake=%s;Gun=%s;ACCs=%s;Grn-Red-Lights=0;MP-MW=%.2f~%.2f;12_Wind=%s;altASL=%.2f;14_AoA=%.1f;15_Payload=%s;16d=0;17d=0;18d=0;19d=0;20d=0;TAS=%.2f", t, "FW-190D9", -- make Simshaker think we have the Dora! myselfData, Engine_RPM, velocityVectors, altAgl, PanelShake, GunFireData, AccelerationUnits, Manifold_Pressure, MW, windVelocityVectors, altAsl, aoa, PayloadInfo, tas ) Most panel arguments are the same as in the Dora. With the exceptions that there is no MW-50 and no cockpit shake. So I set these values to 0. The guns are also a bit different but I think I found a reasonable solution. The only downside is that the effect of the inner MG-151 cannons is not included. I tried to average but could not really figure out the condition you use for triggering the effect. You got some kind of threshold or monitor the change of the value going form 1 to 0? Anyway, a better Gunfire data table would probably look like this: local GunFireData = string.format( "%.2f~%.2f~%.2f~%.2f~%.2f~%.2f", MainPanel:get_argument_value(50), --MG-151 Left Wing (outer) MainPanel:get_argument_value(53), --MG-151 Left Wing (inner) MainPanel:get_argument_value(164), --MG-131 Left Rumpf MainPanel:get_argument_value(165), --MG-131 Right Rumpf MainPanel:get_argument_value(56), --MG-151 Right Wing (inner) MainPanel:get_argument_value(59) --MG-151 Right Wing (outer) ) Plus whatever you do internally with the data, of course. All other effects seem carry over very nicely :D I could not get the Flaps movement effect to work. But then I realized that this is also not working in the Dora. Unfortunately, it seems the the changes of the SimShaker.lua are overwritten with the original each time SimShaker starts and/or DCS starts. So I have to change the file while DCS and SimShaker are running. Edit: Noticed that I can replace the file in the installation directory. Hello Anton :D Have fun in the new home :) PS: You might also want to check the panel shake in the BF-109. Looks like there is a typo: local PanelShake = string.format( "%.2f~%.2f~%.2f", MainPanel:get_argument_value(146), MainPanel:get_argument_value(147), MainPanel:get_argument_value(148[b][color="Red"]9[/color][/b]) -- should be 148 )

I noticed a severe FPS drop when radar range is 60 km as well. So this issue is still present in 2.5.5.33184 It seems it was depended on what is in the "view" of the radar as it did not happen all the time. But when it happened, changing to any other range immediately brought the FPS back.

Thanks!

Still not fixed...

Is this reported? Still present in DCS 2.5.5.33057.

https://wiki.hoggitworld.com/view/DCS_func_getParking Очень хорошая функция :thumbup: Что именно означают переменные "TO_AC" & "Term_Index_0"? спасибо :book:

Not possible unfortunately. You cannot give them any "waypoints" on the ground (just air or landing). The complete taxiing bahaviour after they start up their engines is handled by the internal DCS AI logic and there is not way for us users to influence it.

I gave some planes the task to orbit. When they were out of fuel, they returned to their home base as they should. However, when on final the pilots often ejected. I reckon this might be due to the fact that fuel was empty. Could you please check the RTB condition for the fuel state and confirm that planes have enough fuel to make their way home. This could be slightly off. Thanks.