Leaderboard

I see you guys are active over here. Thanks for your continued interest in the AI Ship mods. I really appreciate it. We have a long way to go with regard to building a NATO and Russian Fleet but we will get there one ship at a time. Thanks HawaiianRyan, I appreciate that. You all's contributions can go a long way with regard to creating more great mods. Thanks for the Liveries Urbi. HighMaintenance also created some beautiful Chinese and Russian Liveries as well. Some samples of his work is below. HighMaintenance, if you like you can post your work here as well to share with the community if you like. Thanks. Thanks ggrewe, I normally add the script at the very bottom of the ships main lua file just above add_surface_unit (GT); -- Also, if for some reason a mod doesn't appear in DCS. Check to make sure the add_surface_unit (GT) has been added. GT.Countries = {'China', 'Russia', 'Argentina',}; Rudel, happy to see you worked it out. bbtbmb the USS Kidd is being reworked as we I write. I found a much better 3d model with better bones. The Kidd at the moment is a Sketchup model. It was the best model i could find at that time. When the Bowen and the Kidd was created I was still learning how to create mods. Still learning. Thanks everyone.

ND424 paint job, Partook in roughly 30 raids before being shot down near Paris on the 28th of June 1944

Hi, Dear Open Mod Manager project followers, this release will probably be the last available on GitHub, here is why: GitHub will soon (October 12th) require Two-Factor authentication and I refuse to comply this, so if there is no alternative (it seem not), I will close my GitHub account before I can't access to it. Don't panic, my projects, including Open Mod Manager are already migrated to SourceForge. So here is the Open Mod Manager project page in SourceForge : https://sourceforge.net/projects/openmodman/ I know Githhub has many advantage and Sourceforge is less user friendly, I myselft currently discover the platform. At least the project will not disapear. Last word to understand my motives: The Two-Factor Authentication paradigm is not security related as claimed, but digital-identification related. I know the future they want for us and I don't like it. Changelog for this release: Automatic README text now generated only if no description is provided https://github.com/sedenion/OpenModMan/releases/tag/1.1

Dear pilots! With this latest development update, we are pleased to announce the successful completion of the intricate flight model tuning process. To mark this achievement, we present our new video showcasing a demonstration flight of the aircraft. From this point forward, we are preparing the module for ED flightworthiness certification. This marks a significant milestone on our journey towards module release!

Octopus-G La-7 Develop update

Couldn't agree more ... currently the only 2FA I'm using is the one of my Bank, because its implemented through a pin-generator device that I carry on my key-chain, not on my phone.

Well done....thanks.

Hey, as with most our missions, I did. I am very happy to hear that you enjoy them - but the credit should not be taken by me alone, the many voice actors and also SMEs who helped with input deserve their fair share, too! Thank you for your very kind words!

First off, I want to be very clear that I understand this plane is in early access, early early access at that, and if I thought for a second this was a matter of waiting for things to be finished I wouldn't make this post. But, these exact issues still haunt the harrier module years after leaving early access, and the nature and consistency of issues point to a failure of management process, design choices, and/or priority rather than a specific technical issue or bug that needs to be squashed. The handling of discreet controls is sub-standard for a module released in 2023. Why are we missing discreet binds? Why are what there are for discreet binds not in their relevant control sections, but instead all thrown haphazardly in a "abstract for joystick" section? Why are rotary axis inverted and only use half their throw as if they were the user-made custom binds instead of properly coded? Why are some many of them broken? Why does it require arcane knowledge to get the idle/stop detent to function properly with a joystick that has them when this has been a standard feature of any module that has them since at least the hornet, and technically even the OG A10 did it if you were rocking the TM Warthog throttle? The entire approach, including even how the control binds menu is organized, just screams management that doesn't realize expectations have changed in this regard since the Huey and original A10 were the marquee DCS modules. This was arguably a failing of the AV8 in 2017; six years later after so many modules have done this so well it just looks sloppy. It feels like the core binds were made to not include physical rotary axis, most multi-position switches made to be toggles bound to push buttons, and then some intern was given the task of cobbling together enough extra discreet and axis binds using clickabledata.lua to make the people with fancy joysticks happy. Contrast this with any Heatblur or mainline ED module released from the F18 onward (2018). With seemingly few exceptions controls binds seems to be made 1:1 with aircraft controls and switch states first, and then abstractions such as cycling toggles or if/else binds added to add accessibility. This is not an issue that will be fixed by collecting bug reports and patching things to minimally workable. This is a structural issue that won't be corrected until RAZBAM realizes that the interface between their simulated systems and the user's physical controls is tantamount to the user experience, and decides to devote some resources to it like it's a proper priority instead of using the same approach that was arguably already outdated in 2017. It doesn't matter how much your pour into in-depth authentic simulation of systems if the people who care about that most are stuck on the other side of an archaic control layer that feels like we're back trying to hack HOTAS controls into Tie Fighter. It's not about bugs or technical issues, those are expected with EA and the positive examples I mentioned all had them--god knows the hornet had nagging controls bugs for years--this is about repeating poor, outdated design choices that are out of place in a full-price marquee module in 2023. Honestly, it feels like RAZBAM still thinks the size of the userbase with switchboxes/panels is still so niche that it's not worth spending more than the absolute minimum amount of resources on us.

This error shows up because you haven't installed them correctly. The mods go into the saved games directory, not into the game installation itself.

'Square withing Square" if because you did not follow the instructions. The website clearly says to disable Lens Effects in DCS https://github.com/mbucchia/Quad-Views-Foveated/wiki#dcs-world Please people RTFM!!

Once you get to where you want to hold focus, Lctrl f11 iirc Some other helpful nuggets here as well. Edit sorry YouTube link didn't come over Sent from my SM-G781U using Tapatalk

Great! Thanks for testing! Perfect!

No problem, thank you for your feedback, I understand your frustration, but if the team have decided to communicate changes as and when they are ready I can not force them. Hopefully we will share more news soon.

That’s incorrect. It is not supposed to release and doesnt.

Practicing formation in the refueling spot

Дорогие друзья! Нынешней заметкой о разработке модуля мы с радостью сообщаем о завершении трудоёмкого процесса настройки лётной модели, чему посвящаем наше новое видео с демонстрационным полётом самолёта. С этого момента мы готовим модуль к ED-сертификации лётной годности, что будет большим шагом навстречу выпуску модуля! null

The reason I don't like VR controllers or buttons on fingers is for me it feels very odd to be waving a controller or my hand around and pressing a button in mid air. I find using either a stick hat or a switch on a button box just feels more immersive. For instance adjusting the altimeter or gunsight by looking at the dial and having the mouse wheel mapped to a rotary switch in front of me works well. Of course if you have enough controls you can map the altimeter to a dedicated rotary but it rather depends how many planes you fly to get it in roughly the right place. The mouse option works well if you want a more generic solution. You can map mouse buttons and wheel functions to multiple physical buttons and switches to cover various parts of the aircraft consoles, e.g left, centre, right or more. It is oddly more satisfying (for me at least!) flicking a physical switch to turn say the battery on (even if it is just a mouse click mapped to it) then pressing a button on a controller. For aircraft which allow right click for on, left for off then the switch matches the animation perfectly. I even have all 20 buttons on Thrustmaster MFDs mapped as left mouse clicks. I just look at the virtual MFD button and press an MFD button in roughly the right place, no need for fumbling around counting buttons. It works for me but I am happy looking at the controls and find I can do this precisely. For everything I need to be operating whilst looking elsewhere during combat I have it mapped to physical buttons & switches.

Hi ladies and gents, does anyone of you know who designed the "Final Hour" missions for the Tomcat on South Atlantic? Those missions are beautifully designed and I would like to congratulate the mission maker. Cheers

Heatblur needs urgently to revise all their missions on operation Reforger II, several bugs are being fixed by users on the web... Mission 1 is ok Mission 2 and 3 can only be completed by fixing some bad triggers (check on youtube) I'm stuck on mission 4 where the Hummes stop before a turn in a point where a pursuit is suppose to happen...(after dropping the second GBU in a armored vehicle) I know this is a free campaign and the missions are really good, but it's very frustating to fly for hours and find out that the mission is impossible to complete because of a broken trigger... You should run the missions before release the content... Please, fix mission number 4 and revise all the others...

Can we get the mother ship, please?

Nobody reading any instructions any more these days? So many problems are just home made.

ED cant just throw mods into the core for multiple reasons: A. Licensing, most mods use models that acquired thru 3rd Party Sites that have strict License agreements. B. Support, the Mod would need to be supported and the mod owner would have to have an agreement with ED to submit their work to ED to be included in each patch. C. Trademark Licensing, ED would have to pay for any TMs included in the Mod as it would be part of a commercial product, as a free distributed mod, it does not. There are a dozen or so more reasons, but those are the main 3.

Neither do I Sedenion. We're being coerced into this kind of thing more and more and the more it goes on, the more I dislike it. Quite literally taking liberties. Open a nice bottle of red.

I ended up with a hybrid solution. Physical buttons, switches and rotaries mapped to dedicated controls and some mapped to mouse functions for controls that aren't directly mapped, so I look at the virtual control and use the closest mouse control to the virtual one - be it a button switch or rotary - in the vicinity (e.g. left, centre or right). Generally I use dedicated controls for things I need to access whilst not looking directly at the control or stuff that is hard to look at (e.g. seat arm, cockpit close, F18 obogs. Mossie fuel controls etc.)

Hello @sedenion - I 100% support and agree with your position. I recommend you update the First Page of this thread to include the Sourceforge URL. The vital thing to know is that you are not alone in your thinking.

Our apologies for the inconvenience, it is on my to-do list but unfortunately got pushed down on the priority list. My apologies for the long wait, it is a sore thorn in my eyes as well. Thank you for your very kind patience.

Commandos - Behind enemy lines. I can still play it today, and it's tons of fun, but it's just not the same as back in the days... because the times, the places, the friends from back then are all kinda gone now. Just like BeatriceDrake said, it's all about nostalgia and memories.

Later down the road, for the second CTU, you'll get JHMCS v1. Still have to add 3D model NVG with banana mount on the helmet. Will come soon.

He just posted this !!

Hi @Nealius Most of the times, most people just bump to afterburner and pick up the stick after wheels up, so maybe most will miss this difference. I believe there is something going on here and have raised this internally. Thanks for the report.

To manually fire the laser in th F-16 you need to press the first trigger detent, but that has nothing to do with Mavericks as the F-16 doesn't have laser guided Mavericks.

Here you go https://www.flightstore.co.uk/product/flyboys-kneeboard-with-clipboard-olive-drab-15468 With this trackball https://www.kensington.com/en-gb/p/products/control/trackballs/orbit-trackball-with-scroll-ring/

Hairy arms?

null

Some additional bindings would allow us to use a normal xbox/PS game controller for the HCU bindings: Castle switch (axis) - Be able to set X and Y axis to make a joystick act as the castle hat. Heatblur have done a similar thing with Tomcat. Trigger (axis) - Setting a trigger to an axis will allow you to use the gamepad triggers as a two stage trigger.

Thanks! The cockpit is on the way. I have implemented a Touch Screen cockpit. Will upload some screenshots maybe a demo later today!

I agree at least by now there should be a thread with a proof of concept and game design and discussion on how A.I will work based on the core code. Seems like ghost and mirrors to keep us in suspense. Although will it ever happen?

That is not a bug, when you get a warning with engines it'll overlay eng page over whatever you have at that moment. Similarly ASE page will be overlayed if you have a warning from there. Manual reference : null

It's important to note that my comment above isn't specifically related to VR. Although the thread is specifically about VR, I thought a slight diversion would be acceptable in order to address some issues in other comments. That said, I am currently running a X570 board with a 5800X3D, 64G RAM and a 4090 (I play at 5120x1440). Personally, after having built custom gaming machines for many years now, I have been fairly impressed with AMD's last few generations - to the point that I built my own as described, after doing others' AMD builds. This is after a lifetime of using only Intel CPUs in my own machines, for what it's worth. Also, FWIW I had just built myself a new Z390/9900K not long before deciding on AMD, after looking at Intel options and not being very impressed at the time. So...if it were me, I'd build an 7800X3D, I think. (To be perfectly accurate, I've been watching pricing for some time now). Again, though, I'd repeat that even the best of current processors will not actually overcome the biggest limitation - which isn't hardware/core count.

Devs answered me. There's no easy way to fix current Su-25(T) flight model for it was made a long time ago. A new FM will be made at some point (no dates), just like there were new FM for other FC3 aircraft.

Beta test feedback is in and looking good. I've made some minor adjustments and am nearly ready to release!

I keep leaning forwards into the hind periscope, expecting to see the lens rendered. Would be really nice to be able to do so so another +1

TB2 UCAV (Turkey) version 1.0.0 released! Changelog Version 1.0.0 Release version

Changes Coming to Sighting Point/Cursor Slews, Snowplow, and VIP/VRP Logics COMING SOON Dear all, In the next update to Open Beta, you can expect a large number of fixes for the DCS: F-16 Viper. Over the past six months, the F-16 team has been revamping the aircraft's air-to-ground sighting and weapon delivery sub-modes to be more authentic and to address many reported bugs in how the F-16 integrates it's sensors, HOTAS, and targeting logic. Along with the upcoming changes to the datalink within the F-16, this has been a very large task that required our dev team to address many aspects of the F-16 all at once, due to the level of integration such changes would require within the aircraft systems. Understandably, this may seem like a lot of changes, but for the most part very little will actually change within the DCS F-16. These changes are mainly focused on ensuring all the minute details that are required for the F-16 avionics to function are properly implemented to prevent any sort of logic conflicts when using the air-to-ground targeting systems. While the Early Access Guide is still receiving revisions to sufficiently explain how all of these weapon delivery sub-modes are intended to work within DCS F-16, we are including a brief conceptual overview for our Viper players to frame the underlying logic in hopes that it will enhance everyone's understanding of why these updates were necessary; until the Early Access Guide can be updated to reflect these concepts. F-16 Conceptual Overview The F-16 sensors (FCR, TGP, and HTS) drive a singular System-Point-of-Interest (SPI). As such, only one sensor can be in a track mode at any given time. When any sensor enters a track mode, it will cause the other sensors to exit their track mode. For example, if the FCR is in Fixed Target Track (FTT) against a surface target location and the TGP enters POINT track, the FCR will exit FTT. This is because the non-tracking sensors must remain aligned to the tracking sensor to maintain the singular SPI location. If two sensors were in track mode simultaneously, the single SPI logic of the F-16 would be violated. When a sensor enters a track mode (FCR FTT/MTT, TGP AREA/POINT, or HAD designation), this automatically puts DTOS, VIS, or EO-VIS into a post-designate state at the corresponding location. The F-16 A-G master mode includes many weapon delivery sub-modes that may be used, depending on the weapon selected on the SMS page. These sub-modes are categorized as either "Pre-planned" or "Visual" weapon delivery sub-modes. "Pre-planned" sub-modes revolve around the use of steerpoints that have been programmed at pre-planned target locations. These sub-modes include CCRP, LADD, PRE, EO-PRE, and EO-BORE. (PRE is used with AGM-154A, GBU-31/38, CBU-103/105, or GBU-24; EO-PRE and EO-BORE are only used with AGM-65) These sub-modes permit direct sighting options (STP/TGT) or offset aimpoint sighting options (OA1/OA2), as well as the Snowplow sighting method. Sighting points are used to ensure the accuracy of the targeting solution to the target steerpoint prior to weapon release. Offset aimpoints are not targets themselves, but are used to ensure the target location (TGT) is accurately placed for weapon delivery (i.e., due to INU drift in a pre-GPS scenario) The selected sighting point determines where the System-Point-of-Interest (SPI) is placed relative to the steerpoint, which directs all sensors to a singular location. Snowplow permits employing a "Pre-planned" weapon delivery mode when existing steerpoints are not practical, and provides a means to rapidly direct the SPI in front of the aircraft at the Snowplow cursor. If a designation is performed while in Snowplow, the main Navigation cursor is slewed to that location and Snowplow is exited. "Visual" sub-modes are geared toward visually acquiring a target location independently of a pre-planned steerpoint. These sub-modes include CCIP, STRF, DTOS, VIS, and EO-VIS. (VIS is used with AGM-154A, GBU-31/38, CBU-103/105, or GBU-24; EO-VIS is only used with AGM-65) Sighting options are not available in these sub-modes, nor is the Snowplow sighting method. The sighting option rotary and the Snowplow OSB options are removed when these sub-modes are entered. These modes will automatically place the FCR in AGR (Air-to-Ground Ranging) and the mode cannot be changed except for placing it in OVRD/STBY. The TGP (if installed) is automatically slaved to the weapon solution in CCIP or STRF sub-modes. The TGP (if installed) is slaved to the TD Box in DTOS, VIS, or EO-VIS sub-modes, even when these modes are in a pre-designate state. This augments the visual identification of targets and assists in optically locating targets at extended ranges. When a target location is designated in DTOS, VIS, or EO-VIS sub-modes, this also updates the current steerpoint location by moving the Navigation cursor to the same location. This ensures a seamless transition between sub-modes (Example DTOS->CCIP->CCRP) against the same target location in which the SPI is maintained on the target. Visual Initial Point (VIP) and Visual Reference Point (VRP) sub-modes are a means of conducting strikes against pre-planned target locations in CCRP sub-mode while using visual landmarks for final alignment of the targeting solution. These are especially useful when conducting low-level strikes in which the target may not be visible until just prior to weapons release. These sub-modes permit cursor slews to be performed to align the targeting symbology with visual landmarks without affecting the cursor deltas of the main Navigation cursor. VIP adds "IP" as an additional sighting point option that may be selected using TMS Right-Short while the HUD or FCR is SOI, or by pressing the corresponding sighting point rotary at OSB 10 on the FCR or TGP MFD formats. When VIP mode is entered, the sighting point is automatically set to "IP", after which the sighting points may be advanced in a sequence of IP->TGT->OA1->OA2->IP. VRP adds "RP" as an additional sighting point option that may be selected using TMS Right-Short while the HUD or FCR is SOI, or by pressing the corresponding sighting point rotary at OSB 10 on the FCR or TGP MFD formats. When VRP mode is entered, the sighting point is automatically set to "TGT", after which the sighting points may be advanced in a sequence of TGT->OA1->OA2->RP->TGT. These modes allow a single overfly designation of the IP or RP in which the SOI is automatically set to the FCR and the sighting point is set to the TGT. This allows a seamless transition with one button press from the ingress phase into the final attack phase, without the requirement to manually slew the cursor to align the diamond symbol in the HUD with the physical landmark that represents the IP or RP. Changelog: Sighting Points & Cursor Slews Cursor slews are now possible in several different modes that are independently accumulated. As an example, the VIP cursor may be slewed and zeroed independently of the Navigation cursor. If Cursor Zero is pressed and "CZ" remains displayed on the MFD, it is because another cursor still has cursor slews applied. This may be seen when the DTOS/VIS cursor is zeroed back to the FPM, but the main Navigation cursor may still be slewed away from the original steerpoint location. To zero the Navigation cursor, CCRP or CCIP should be entered and then CZ pressed. When cursor slews are applied, Cursor Zero is needed to remove them. For a time, changing the selected steerpoint was erroneously zeroizing the cursor when it should not have been. This has been rectified so that cursor deltas are maintained during steerpoint switching (ie, if the TGP was looking 500 meters west of steerpoint 1, it will be looking 500 meters west of steerpoint 2 if the STPT is advanced from 1 to 2). The TD Box occludes the steerpoint diamond. If they are co-located, which is the case in "Pre-planned" A-G sub-modes like CCRP or LADD, the steerpoint diamond will be hidden by the TD Box. When the steerpoint is slewed using the cursor, the OA1 and OA2 offset aimpoints will always slew with it to maintain their programmed offset distance/direction as entered on the DED DEST page. Pressing Cursor Zero no longer zeros the OA1/OA2 settings. These can only be zeroed by manually editing the RNG value to 0 on the DED DEST page. If the RNG value of OA1 or OA2 is set to 0, the OA triangle symbols will be removed from the HUD/HMCS and will not be available in the sighting point rotary options. OA1 and OA2 will not be available in the sighting point rotary options if FIX or A-CAL are displayed on the DED. When not in VIP or VRP modes, the OA1 or OA2 triangle symbols will not be displayed in the HUD/HMCS if not selected using the sighting point rotary option. When in VIP or VRP modes, both OA triangle symbols (if RNG is not 0) are always displayed along with the IP/RP diamond, TGT TD Box, and PUP circle symbols. Sighting point options are not available if in any "Visual" weapon delivery sub-mode: CCIP, STRF, DTOS, or VIS; or if MARK is displayed on the DED with "HUD" as the marking method. Sighting points may be cycled using TMS Right-Short while the HUD or FCR is SOI (prior to this it was only possible with FCR as SOI). The "Ghost A-G Cursor" (white crosshairs) is now displayed on the HSD at the current sighting point location for all sighting points (including OA1, OA2, IP, and RP). Prior to this it was only displayed when TGT was the selected sighting point. The Azimuth Steering Line will only be referenced to the TGT sighting point location, even if the sighting point is changed to OA1, OA2, IP, or RP. Only the direct sighting point (TGT) can represent the target solution for weapon delivery; offset aimpoints only assist in alignment of the targeting solution. Only one sensor can be in a "track" mode at any given time, since the SPI represents the location to which all aircraft sensors are directed. Entering a track mode in one sensor will cause other sensors to break lock. If FCR enters FTT or MTT, the TGP will exit POINT/AREA track and any HAD designation will be dropped. If the TGP enters POINT or AREA track, the FCR will break FTT/MTT lock and any HAD designation will be dropped. If a threat radar symbol is designated on the HAD, the FCR will break FTT/MTT lock and the TGP will exit POINT/AREA track. If the sighting point is changed, the aircraft sensors will exit their respective tracking modes to prevent cursor slews from being erroneously input into the system. The TGP is automatically slaved to the DTOS/VIS TD box while in pre-designate state. If in DTOS/VIS sub-mode and a sensor is commanded into a track mode, the sub-mode will automatically enter post-designate state at the corresponding sensor track location. (ie, if the TGP is SOI and being slewed in DTOS mode and commanded to POINT track, DTOS will enter post-designate at that location) If in any "Visual" weapon delivery sub-mode (CCIP, STRF, DTOS, or VIS; or if MARK is displayed on the DED with "HUD" as the marking method), the FCR will enter AGR mode and cannot be changed. FCR mode selection page is corrected to prevent manually changing the FCR out of AGR mode without changing the weapon delivery sub-mode. When a laser-guided bomb is selected in SMS, the TGP laser will be inhibited from firing if the sighting point is set to OA1, OA2, IP, or RP. This prevents an LGB from being diverted from the intended target location, which is represented by the direct sighting points of TGT or STP. Snowplow Snowplow is only available while in a "Pre-planned" weapon delivery sub-mode: CCRP, LADD, PRE, EO-PRE, EO-BORE; or if in NAV mode if the FCR is not in an A-A mode. When Snowplow is entered (via OSB 8 on the FCR or TGP MFD formats), the SPI is placed at the location of the Snowplow cursor in a pre-designate state (represented by the TD Box in the HUD). In NAV mode when there is no TD Box and the steerpoint diamond represents the steerpoint location, there will be no HUD symbology corresponding with Snowplow cursor while in a pre-designate state. If TMS Up-Short is pressed while the HUD, FCR, or TGP are SOI, Snowplow is exited via post-designate and the main Navigation cursor is moved to the location of the SPI (represented by the TD Box in A-G master mode or the steerpoint diamond in NAV master mode). If Snowplow is exited from pre-designate by pressing "SP" at OSB 8 on the FCR or TGP MFD formats, the SPI simply returns to the existing location of the main Navigation cursor since a designation was not performed. The Snowplow cursor location is placed in three dimensions by the following. Aircraft Heading: The cursor will remain along the aircraft longitudinal axis and cannot be changed. Range: The cursor will be placed in front of the aircraft at 50% the A-G FCR range. Adjusting the FCR range (even if the FCR is in OVRD or STBY modes, or if the RF switch is in QUIET or SILENT) will move the Snowplow cursor in range. If the FCR is powered OFF on the SNSR PWR panel, the Snowplow cursor is fixed 5 NM in front of the aircraft and cannot be changed. Elevation: The cursor is set to the same elevation as the current steerpoint while in pre-designate. When Snowplow is exited via post-designate, the elevation of the SPI is re-calculated to the terrain elevation. When weight-on-wheels, the cursor is set at the same altitude as the aircraft. VIP/VRP It is no longer possible to enable VIP and VRP for the same steerpoint. Enabling one mode will disable the other if set to the same steerpoint. When VIP or VRP mode is entered, a Cursor Zero is no longer performed to the main Navigation cursor. When an overfly designation is performed in VRP mode, the designation will now designate the location of the RP, not the TGT. Only one overfly designation may be performed of the IP in VIP mode or the RP in VRP mode, using TMS Forward-Short while the HUD is SOI. Cursor slews may still be performed before or after the designation, but VIP and VRP modes must be exited and then re-entered to perform subsequent overfly designations. When entering VIP mode, the EHSI will be directed toward the IP and the Azimuth Steering Line will be to the TGT. When an overfly designation of the IP is performed, the EHSI will switch to the TGT. When entering VRP mode, the EHSI and the Azimuth Steering Line will be to the TGT, even after an overfly designation of the RP is performed.

Google desperately want your phone number because it helps them tie all the other things they already know about you to a device that tracks your location to within a few feet ( to a few inches in the case of Crapple phones - allegedly ) There is no end to the uses they can put this to learn more about you, which makes their data profile of you more valuable to advertisers. Most people don't care, but then most people don't really understand the extent of Googles spying. I am unwilling to have my very existence monetized for their own benefit by a morally bankrupt corporation, so I won't be installing their Authenticator. If ED ever requires me to give a phone number to Google just to use DCS then I will stop using it.

In game they don't. And AI sees through them too. (kinda a big deal for WW2 stuff). Also so do optically guided AAA, as of course any IR manpads. Also targeting lasers go right through them as well. IRL of course cloud cover was a major tactical issue. In DCS, well... I guess its not that important.

Potrebbe essere un problema legato all'affinity mask e alla tua particolare CPU, visto che intel ha iniziato a creare CPU con architettura "BIG-LITTLE", ovvero affiancando core con diverse performance. Potrebbe essere che in realtà sta piazzando del carico sugli efficency core che sono totalmente inadeguati per eseguire operazioni legate a DCS. Appena ho tempo provo a indagare se c'è modo di fare l'override della maschera di associazione delle CPU e ti faccio sapere, probabilmente sarà poi da capire quale "codice" utilizzare per la tua specifica cpu.