shagrat

Stimmt so nicht ganz, ich meine es wird ein Kontrast zum Hintergrund er-/gemittelt und der fliesst als Faktor in die Kalkulation für das "Spotting" mit ein. Das Problem mit der KI ist, hat sie dich erstmal gesehen, weiss die ganze Gruppe wo du bist und sie verliert die Sicht nur wenn du wirklich die LOS unterbrichst. Aber es macht anscheinend tatsächlich einen Unterschied, ob du gegen den hellen Himmel sichtbar bist, oder eine Berg-/Hügelkette hinter dir hast. Ebenso wie "Dunst", Tageslicht etc. den Kontrast beeinflussen. Nur Nacht und optische Sensoren sind etwas "merkwürdig", da die KI ohne IR quasi blind ist. Die "Strassenbeleuchtung" hat anscheinend keinen Effekt auf die "Sichtbarkeit". Ich konnte nachts mit einem Huey, mal auf 20m im Tiefflug an eine ZSU-23 ranfliegen und landen, dann mit der Minigun (kurz in den Doorgunner gewechselt) die ZSU ausgeschaltet. Die hat mich nicht sehen können, obwohl ich fast genau unter einer Laterne stand. Ist aber auch schon ewig her... Müsste man aktuell testen. P.S.: natürlich hat der KI-Doorgunner auch nix gesehen, weil war ja finstere Nacht.

Solange du das Fenster aufmachst und am Geruch erkennst, ob es ne russische MiG-29 oder ne F-4 ist, gebe ich dir recht... Ansonsten gehe ich einfach Mal davon aus, dass die Fachleute der entsprechenden Streitkräfte ihre (guten) Gründe hatten ihre Jets so zu bemalen/tarnen, wie sie es getan haben. Das Einsatzprofil bestimmt den taktischen Nutzen. Ein "so muss das Aussehen" gibt es halt nicht. Natürlich, können wir jetzt jeden Einzelfall durchkauen und das für und wieder bei jedem Einsatzprofil diskutieren, aber ich denke, die Leute deren Leben und Missionserfolg von solchen Dingen abhing, wussten schon was und warum sie da tun.

Der Nutzen ist ja nicht der Punkt, es geht um den individuellen Geschmack... Wobei in DCS es tatsächlich einen Unterschied machen wird, wie gut du eine getarnte Maschine vor einem begrünten Hintergrund siehst. Schön am Bild mit der leuchtenden F-16 im Vordergrund zu sehen... Dunkle Livery gegen hellen Himmel oder dunkle Livery vor dunkel bewaldetem Hügel, macht durchaus einen Unterschied. Wenn du natürlich nur aus grosser Höhe Bomben fallen lässt, macht hell/grau schon Sinn, aber die bunten "komm lass uns Ritterspiele machen" Bemalungen, haben in der Tat, wenig taktischen Nutzen... aber wenn es dem Piloten-Ego hilft? In modernen Streitkräften siebt man diese stark egozentrischen Typen heutzutage eher aus... Das gute ist in DCS werden wir uns ganz individuell unsere Liveries aussuchen können. Und notfalls gibt es bestimmt zeitnah alle möglichen aus der Community. Also am Ende sind hoffentlich alle glücklich.

Mod ≠ Module Mod = Modification (you can Google it) The DCS folder Mods is the abbreviation for Modules, but does not reference community Mods... and yes, it is somewhat confusing.

No, nix dagegen.

I wasn't addressing the community, just pointing out, that it is a bit strange to emphasize the value of your personal time while asking others to invest their time in doing a review for you... Especially, as the UH-60L comes with one of the best install guides and manuals, I've seen for a community mod. So why you won't just read the manuals 2 pages on the install and setup of the 4-axis (cyclic, pedals, collective), everything else is clickable in cockpit. Just my 2 cents.

No, nothing like an indicator or light. You must remember to hold FTR and release it after you have stable course and attitude. My biggest issue is, when I accidentally "wobble" the button, as I don't concentrate and it is recognized as multiple presses, quickly changing the center. That's where you need "Trim reset" to adjust the trim back to the physical center. This "trim reset" is a DCS thing, the trim / FTR in the real aircraft doesn't move the physical center, but keeps the stick and counterforces at the "new" position of the stick after trimming. Basically it has no spring that enforces a center when the stick is upright, but "creates" a center at the current stick position when you release the FTR... Hope that is understandable.

Oh, that was a bug in the Huey, as well, for quite some years... I have more issues with the excessive speed, but it's basically what is early access and I am very happy with what we have so far.

Try setting up a demo mission in the Mission Editor, put a UH-60L on the ramp, with Skill: "Player", Waypoint: "Start from ground engine on". That way all systems are set and on. Do you have the same behavior? If not, it's likely any or some of: SAS 1 & 2, Boost not activated or Stabilizer not in "Auto". If the behavior persists, I would look into my controls setup. Multiple Axis assigned to the same? Only one Column should have an Axis set in any row! Axis set inverted/not inverted, Setup correct? Check with RCTL+RETURN that axis follow the inputs as expected. Check you use Force Trim Release correct. Press and hold FTR while you maneuver, do NOT just click it multiple times, as it will quickly re-trim your center. Again, monitor the Controls overlay, the red diamond is your stick position, blue the trim, green seems to represent the SAS corrections...

Well, then it's simple. If you can't be bothered, don't bother... Why should someone waste time on writing it all down, if you may not try it anyway? Instead we could spend that time much better doing some flying... Why is your time more precious then other people's?

Einfach die Koalition "Joint_Task_Force Blue/Red" oder "UN_Peacekeeper" wählen und es stehen ALLE Einheiten, und mittlerweile meist auch Skins, zur Verfügung. Das nutze ich eigentlich nur noch, wenn mal wieder eine bestimmte Einheit irgendwo fehlt.

Jupp, quasi. Nur, dass er zusätzlich auch einen Trim Hat hat, ähnlich der Gazelle.

Hab hier durch die Virpil S-Verlängerung Saturation-X am Cyclic auf 70% und Curvature auf 15. Ohne Verlängerung, solltest du die Saturation-X auf 100 lassen und evtl etwas mehr Curvature. Ich hatte jetzt stumpf im Cockpit auf den Cyclic geschaut und mit meinem physischen Stick verglichen, dass die ungefähr die gleichen Wege zurücklegen, so Pi mal Auge. Pedale Curvature 10 und Saturation-X auf 90 damit ich nicht bis ganz auf Anschlag durchtreten muss. Collective wieder nach Auge die Wege angleichen, aber da ich ein Virpil Collective habe, das ich bis unter die Achselhaare ziehen kann, muss ich die Achse eh zwingend begrenzen, da hilft dir mein Wert nicht.

Ja, ist es. Nur FPS ist default deaktiviert. Der UH-60 sollte grundsätzlich mit SAS geflogen werden. Der "Trick"ist, bei jedem Manöver den Trim Release gedrückt zu halten und erst loszulassen, wenn er stabile Lage hat. Dann nur Mikrobewegungen zum Kurs halten. Wenn du versuchst wie beim Huey den Trim kurz zu drücken, geht das schnell in extremste Fluglagen über, die ich nie gewollt habe. Muss man sich erst dran gewöhnen.

Just press RCTRL+RETURN to activate, like in every other module. Sound is the two turbines and a modern Rotor without the Huey's thundering "Flap-Flap"... It could be a little louder and more pronounced for my taste, especially in cockpit. And we need the volume going up, if the slide doors open.

Just to point out, the F-14 is used in MP, just not a lot in competition aka "Player vs Player"...

Make the overlay visible by default, would fix the "awareness". Anyway, just think about multiple "newbies" to radio ops popping into servers, using the radios to "talk" to the other guys, unaware of the implication and basically blocking/jamming the frequency intermittent. Either everyone else is switching to another frequency (so they can't here them anyway) or they get instructions on how to use / get on the radio, and then there's no problem to add a "first click on the antenna icon, when ready to switch to radio comms mode". But if they run into problems, the default coalition room would be active and any experienced player, just needs to switch back to room and pick them up and help them, with bi-directional comms. Experienced players will simply activate the "switch to radio on start" option.

A couple things I would like to see: mic click. Can be placeholder, or a simple "beep" to know the radio transmits the ability to assign different keybinds to the cockpit PTT buttons per each(!) module. This is crucial to address flying planes AND helicopters as you need PTT on different controllers, namely throttle vs. joystick! E.g. F/A-18C COMM switch is on the throttle, in the Mi-24P or AH-64D you have PTT on the cyclic! Room PTT should work with any PTT pressed. Apart from that the implementation is very promising. If we get the effects like "radio/distortion", realistic squelch, clicks, encryption sounds this will be a big ease of use for multiplayer comms.

Same experience here. This is making multiplayer with super carrier a bit awkward. One idea we thought about yesterday, was to have a quick press and release popup the normal in-game F-Key Menu and press and hold activate voice.

To have radio as "default" when entering a cockpit, there is an option in the settings. I personally think it's better to have room mode, by default, as especially newcomers to Multiplayer struggle with operating the radios. It's easier for an experienced player/instructor to explain radio and the voice chat in a "room", then show how to switch to the radio mode. Not everyone is an experienced player.

If you use the non-steam version of DCS World, there is a Free-to-play program, where you can test any module for two weeks. This way you can see, if it suits you. Just visit digitalcombatsimulator.com and try any module before you decide to buy it.

Yeah, you may need to adjust the ranges a bit. After a getting used to it, I twist the throttle more quickly and needed to adjust the Increase Throttle zone a bit. 59-63%... just try until it moves the twist-grip in-game out of cut-off to idle stop.

See my post directly above yours.

For everyone who wants to use the throttle axis and idle stop. This was the closest I could get it to work as intended. 1. Check the Y-Axis is not invertes in the VPC Config it shouid match the rotation direction in DCS without having to invert the axis in DCS. If you need to invert it in DCS to match, you need to adjust this n the VPC Configuration, not DCS ! To get to that setting DOUBLE CLICK the axis (See second picture where to adjust). 2. Define 2 different "Axis to button setups to create 2 additional "Buttons". (Ignore the 3rd I created, this is not necessary for this setup) 1st for Axis 2 from 91% to 99% and a free physical button number (depends on your twist grip). This will create a button press when the throttle is just moved a little bit counter-clockwise and will be our "Decrease Throttle" button later in DCS. 2nd for Axis 2 from 60% to 62% and the next free physical button number. This will create a button press just before the physical idle stop and will be our "Increase Throttle" in DCS to push the throttle from shut-off into idle position, when e twist the twist grip through the idle stop detent. You may need to adjust these values to your physical axis, in general they should be close enough. 3. Next we need to assign the "new physical buttons" to a logical button press! To do so open the buttons menu. Ensure the buttons show as axis to button in the black field below the button list. Select 2 free Logical Button and assign the new buttons to them as a "Normal" button press. Also make sure you have the IDLE STOP button assigned. By default it should be button 1, unless you configured it different. The logical button number does not really matter, but you need a logical button assigned. That' the setup in the VPC Configurator. AND DON't FORGET TO SAVE THE SETTINGS TO THE DEVICE. MAKE SURE YOU CONFIGURE THE ROTOR TCS PLUS ! You may check the buttons in the VPC Joy Tester, now. Do NOT check with the overview of the physical setup on button page. Always check with the VPC Joy Tester to see the Logical button output. If everything is working as expected (Buttons from the twist grip axis turn ON and OFF when twisting through the axis positions, switch to DCS. 4. Setup the throttle axis in DCS. Open the Axis Controls in the DCS Control Setup Menu, select Throttle (in the Pic it's "Schubhebel" as its in german), go to the "VPC Rotor TCS Plus column and assign the JOY_Y axis (Grip-Axis). Now right click the JOY_Y field and select the axis tuning menu. Make sure to check the "Slider" option and do NOT check the "Invert" option. If the twist grip axis in DCS does turn in the wrong direction, go back to the VPC Config and adjust it there. Tune the "Saturation X" to 58/59 so that the flat part on the top ends where the red DOT is, if the twist grip is in the idle position. That is when you twist beyond the idle stop, to full and back against the idle stop. This enables us to use the full throttle axis in DCS with just the part of the physical axis that goes from idle stop to full open ! 5. Set the key bindings for the Increase and decrease throttle buttons. We need to assign the "IDLE STOP" to the idle stop on the collective (default JOY_1) and now the button at the nearly full clockwise (closed) position to "DECREASE Throttle" and the button from the close to idle stop position to "INCREASE throttle". Save the setup with "OK" In DCS you should now be able to twist the throttle through idle stop and the throttle should snap to idle, due to the short "INCREASE" button press. When you twist back and press IDLE STOP the idle stop in game should be depressed and you can twist to the shutoff position until the "DECREASE" button is "pressed" and shuts down the engine. The only drawback I could find is, that during startup you will need to have the throttle in idle and not "just below the idle stop", but that works without problems, it seems.

That's why his scenario contained "supposedly" balanced aircraft. The point is, if you balance number of players (red vs. blue) the best thing a mission designer can do is putting the exact same aircraft and weapons on both sides...