shagrat

In MP it still occurs, no matter the setting of George (realistic OR simple). It happens with the Host, as well as a client. the CTD is happening on the individual PC, where you command George t osearch PHS LOS. We could reproduce it on both client and host in the same mission. PHS LOS with reticle over the area with blue and red groups and prompt CTD.

CoreMods contains all the AI modules to be available in any kind of mission, typically populating airports or acting as AI-aircraft flying in the sky around you. Depending on what the Instant action, training mission, single player mission contains, it WILL cause issues. Only if you create ALL your misssions yourself and don't add any of these assets as AI or static objects, this may work. As said by others, as this is part of the DCS core installation, every update will repair the missing files...

Same here, it's reproducable. I have two groups at the position I scan, that are set to AI OFF at the time of commanding George to scan LOS PHS. Immediately after positioning the TADS, the crash occurs. The log shows the same error with the sound files ("slavin.ogg" etc.) LOG: 2024-12-27 16:16:50.245 ERROR ED_SOUND (20312): can't load wave: "speech/eng/ah-64d/george_cpg/slavin.ogg" 2024-12-27 16:16:51.146 ERROR ED_SOUND (20312): can't load wave: "speech/eng/ah-64d/george_cpg/deslavin.ogg" 2024-12-27 16:16:51.680 INFO EDCORE (Main): try to write dump information 2024-12-27 16:16:51.758 INFO EDCORE (Main): # -------------- 20241227-161652 -------------- 2024-12-27 16:16:51.758 INFO EDCORE (Main): DCS/2.9.11.4686 (x86_64; MT; Windows NT 10.0.22631) 2024-12-27 16:16:51.758 INFO EDCORE (Main): D:\DCS World\Mods\aircraft\AH-64D\bin\AH64D.dll 2024-12-27 16:16:51.759 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff8bc01375c 00:00000000 2024-12-27 16:16:51.759 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'D:\DCS World\bin;', symOptions: 532, UserName: 'user' 2024-12-27 16:16:51.760 INFO EDCORE (Main): OS-Version: 10.0.22631 () 0x100-0x1 2024-12-27 16:16:51.761 INFO EDCORE (Main): 0x000000000045375c (AH64D): ExternalFM::AH64::AH64FM::setImmortal + 0x1D3C 2024-12-27 16:16:51.762 INFO EDCORE (Main): 0x0000000000453a24 (AH64D): ExternalFM::AH64::AH64FM::setImmortal + 0x2004 2024-12-27 16:16:51.762 INFO EDCORE (Main): 0x0000000000442c07 (AH64D): ExternalFM::AH64::AH64FM::getSensorsSystem + 0xB7B7 2024-12-27 16:16:51.762 INFO EDCORE (Main): 0x000000000000e2e0 (edObjects): Evoker<LandObjectDestroyNotifierBase,Link<LandObjectDestroyNotifierBase> >::onStartEvoke + 0xD0 2024-12-27 16:16:51.762 INFO EDCORE (Main): 0x0000000000011412 (edObjects): viSearch::TestAndInsert + 0x52 2024-12-27 16:16:51.762 INFO EDCORE (Main): 0x000000000001d528 (edObjects): DamageInfo::GetDamager + 0x15A8 2024-12-27 16:16:51.763 INFO EDCORE (Main): 0x000000000001d5fe (edObjects): DamageInfo::GetDamager + 0x167E 2024-12-27 16:16:51.763 WARNING LOG (23112): 11 duplicate message(s) skipped. 2024-12-27 16:16:51.763 INFO EDCORE (Main): 0x000000000000b77f (edObjects): viObjectManager::GetObjects + 0x9F 2024-12-27 16:16:51.763 INFO EDCORE (Main): 0x000000000000c1fb (edObjects): viObjectManager::GetSegmentList + 0x9CB 2024-12-27 16:16:51.763 INFO EDCORE (Main): 0x000000000045b3a8 (AH64D): ExternalFM::AH64::AH64FM::setImmortal + 0x9988 2024-12-27 16:16:51.764 INFO EDCORE (Main): 0x000000000045cb7b (AH64D): ExternalFM::AH64::AH64FM::setImmortal + 0xB15B 2024-12-27 16:16:51.764 INFO EDCORE (Main): 0x000000000046015f (AH64D): ExternalFM::AH64::AH64FM::setImmortal + 0xE73F 2024-12-27 16:16:51.764 INFO EDCORE (Main): 0x000000000021f70e (CockpitBase): cockpit::avDevice_BasicTimer::NextEvent + 0x1E 2024-12-27 16:16:51.764 INFO EDCORE (Main): 0x00000000000045eb (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB 2024-12-27 16:16:51.764 INFO EDCORE (Main): 0x0000000000004c12 (World): wSimCalendar::DoActionsUntil + 0x262 2024-12-27 16:16:51.764 INFO EDCORE (Main): 0x000000000091459a (DCS): SW + 0x427ACA 2024-12-27 16:16:51.764 INFO EDCORE (Main): 0x0000000000914271 (DCS): SW + 0x4277A1 2024-12-27 16:16:51.764 INFO EDCORE (Main): 0x0000000000939b72 (DCS): SW + 0x44D0A2 2024-12-27 16:16:51.764 INFO EDCORE (Main): 0x00000000008f3fb4 (DCS): SW + 0x4074E4 2024-12-27 16:16:51.764 INFO EDCORE (Main): 0x00000000008f56e3 (DCS): SW + 0x408C13 2024-12-27 16:16:51.764 INFO EDCORE (Main): 0x0000000002265047 (DCS): AmdPowerXpressRequestHighPerformance + 0x11D2043 2024-12-27 16:16:51.765 INFO EDCORE (Main): 0x0000000000cd4182 (DCS): SW + 0x7E76B2 2024-12-27 16:16:51.765 INFO EDCORE (Main): 0x000000000001259d (KERNEL32): BaseThreadInitThunk + 0x1D 2024-12-27 16:16:51.943 INFO EDCORE (Main): Minidump created. dcs.log-20241227-161652.zip

Dir und deiner Familie auch ein schönes und vor allem ruhiges Weihnachten! Vielen lieben Dank. Liebe Grüße, Shagrat

I really hope this is still developed. Especially flechette munitions and the option to create mixed loadouts individually. The flechette rounds are great if you need directed area effect against infantry and light vehicles with no explosive and blast damage. ...and the support of configurable zones with mixed loadouts is one of the most versatile aspects, of the FFAR rocket system, on modern helicopters.

I am pretty sure it was the hardware and technology available at that point in time they were created. As the terrain resolution/height mesh is more or less the foundation, it's not that simple to add a better mesh later. Basically you would need to start from scratch... texturing the mesh, fix the rivers, roads, powerlines that will break, then review and redo most/all of the cities/populated areas, etc. ...and there must be elevation data available in such a high resolution, in the first place. Not something you can download from anywhere and use in a commercial product.

Can you post a picture in your new robes?

Yep, makes using the radios a pain in the back and entering frequency only really possible on the ground. Please ensure the "Channel Select Switch LEFT [KYBD]" is fixed, as well. Seems it's broken, too. Thanks in advance.

It's not the animation. The Keybinds are bugged. AFT (CH DN) bound to a key or button triggers FWD (CH UP) so that you can only increase the channel, but never decrease. What's even worse, the LEFT (KYBD) bind doesn't work, as well. So even staying in manual and changing the frequency manually isn't an option. To use the mouse on the collective Channel Select Switch via left clicking the buttons, is only practical on the ground! This should be a priority fix!

Du hast bestimmt recht, alle deine Vermutungen basieren auf soliden Annahmen und müssen deshalb stimmen...

Ich sag mal so, wenn du zum "fliegen" 10-15 Minuten "Aufbau und Einschalten" einplanen musst, hast du vermutlich genug Peripherie und Kram, um als "Rig" durchzugehen... im Prinzip geht es ja um das Equipment, das je nach Geldbeutel langsam oder schnell von einem "einfachen Joystick mit Twiststick" zu einer - mehr oder weniger exakten - Nachbildung eines realen Jet oder Helikopter HOTAS mutiert. Panels bauen und ACES II Seat auf Ebay ist dann so das "Endstadium"... so man den Platz dafür hat.

Das stimmt so sicherlich für dich, aber ob das auch all die 90% die da anführst auch so sehen,wage ich zu bezweifeln. Es gibt ziemlich sicher mehr(!) Menschen die "bevorzugt" oder ausschließlich Singleplayer spielen, aber der Anteil Multiplayer steigt auch kontinuierlich. Kaum jemand wird mit einem Homecockpit-Bau in DCS einsteigen, aber zumindest diejenigen, die über mehrere Jahre dabei bleiben, beginnen eigentlich fast alle, nach und nach sich HOTAS, Pedale, Headtracker, VR, MFD-Rahmen, oder Button-Boxes zu holen. Nicht alles auf einmal, oder nur Teile, aber wer DCS nicht nur mal, als "Air-Quake" oder zum "Schauen", für ein paar Monate anschmeisst, wird i.d.R. Interesse an einem guten und passenden Rig bekommen. Ausnahmen gibt es natürlich immer, vom Spezi der mit Tastatur und Maus fliegt, bis zum dem YouTuber der mit Xbox-Controller fliegt.

So if we replace the carrier dudes with the airshow crowd as a stand in for people at an afghan market and drop cluster bombs on those, we are obviously fine, right?!

"Random carrier dudes"?! Really? ...just, wow!

You misunderstood, we can place, for example the unarmed sailor or a flight director, or a white/red/yellow shirt everywhere we like, as "unarmed" persons... or use innocent cows. And as I said, we can level whole civilian city blocks, if we choose to. That's why the "supposed" reasoning against "civilians" in a simulation doesn't make a lot of sense. And if that's the concern, just make them without a death animation, but have the model register hit/dead events so we can simulate the challenges and restrictive nature of typical ROEs in such a theatre. Currently it's mostly a decision along the line of "if it moves, shoot it!". I would like to make players actually think and consider potential collaterals or bomb impact ranges etc. to make COIN missions much more interesting and challenging.

@TheTrooper Thanks to you both! That's exactly(!) what I was looking for. I understand what you mean with the HLS. Too much gras, missing concrete areas and access ways for the ambulances. I used the "Aztec Hill" FARP to get a single landing pad, that fits the Chinook. Not perfect, but better as the scenery as it has at least a smooth surface and big enough... we really need concrete slabs of different sizes, that can be placed as HLS.

@TheTrooper Can you post the coordinates of the Bastion hospital and HLS or mark it on a photo on a screenshot? I'm trying to setup a dynamic environment with a scripted Medevac component for the Chinook, but it is hard to find details about the exact position of things like the hospital.

The tactical aspects (no go zones) etc. is up to the Mission builders and you can already create a LOT of stuff with mission scripting. What we really need is assets, especially civilian/environment stuff, like the pickup trucks without armement. The insurgent model without the Ak (unarmed) etc. to make a living and breathing world and to finally be able to create meaningful representation of Rules Of Engagement. Especially with all those asymmetrical conflict focused maps, where ROEs are a key element to the tactics and restrictions.

We already have Deck crew and personnel to place, which is unarmed, as well. Apart from allowing to make the maps feel more alive, it would actually enable mission designers, to create meaningful conditions that reflect ROEs. Especially in the asymmetrical conflicts in Afghanistan, Syria and Iraq, the Rules Of Engagement, the need to ensure no harm to non-combatants, is a key tactical element! ...and if someone is concerned about "civilians": laying waste to whole city blocks, afghan villages and fields of crop, is not exactly the Geneva convention spirit, either, despite being simulated in DCS.

I agree with Opal 4-1, as it's not any unimportant elevation somewhere in the middle of nowhere, but an important landmark and place of one of the more important outposts to setup a realistic UK area of operations. Now Zad had two major military landmarks, the District Center and ANP hill. Nobody would suggest to painstakingly recreate every hill and ridgeline, but if google "ANP Hill" or read Ed Macy, etc. it's actually an important place in a map designed to recreate Afghanistan during OEF respectively OP Herrick.

The thing is the dev of rotor ops is hosting a server since a while and uses a lot of dicord integrated scripts there. So it inevitably moved to discord for discussion, server lobby, and overall feedback. There's still the landing page: https://dcs-helicopters.com/ and of course the GitHub: https://github.com/spencershepard/RotorOps Discord is: https://discord.gg/rotorops

I downloaded the Manual for the WinWing F-16 Grip. I have a Virpil CM-50.2 on a Rhino base, so very similar, but not the same. From the button overview it looks like the F-16ex has the same axis and button in parallel setup the CM-50 uses, BUT it has two(!) buttons emulated on the axis (or an additional physical button, at the end of travel ?) I just checked the paddle lever (button emulation) with that button press and off state for extend/retract and l get the same phenomenon. It works once, then it doesn't react to the pedal button anymore, though the keyboard commands still work. I tend to suspect a bug here, that's not related to the hardware or configuration. It should work exactly like this. And this is unrelated to the paddle button, as I get the same behavior with other buttons off-state - works once.

No, this is now possible directly in the DCS configuration menu. So you only need to ensure in Simapp pro the paddle button is sending as long as it's pushed, that's usually a default on most software like Simapp.

You may try "pulled paddle"(Button 8?) = "Extend" then select "Retract" and manually select the now available option Button 8 Off. Ensure the Paddle is configured as a constant pressed button in the device software (winwing). The result should be: Paddle pulled (sends button 8 press and hold) and uf you release, it recognizes button 8 Off and should retract.