sa63114200

Last post... The path to my Saved Games wasn't corrupt but it was pointing to D drive where in my gaming desktop I have a second SSD to house DCS and MSFS. When I cloned the Windows SSD, I debated whether to create two partitions in my laptop SSD or have everything in one. That decision is where things went south in regard to Model Viewer. At any case, with the huge increase in sizes of DCS and MSFS (300G and 600G respectively for me), we are all adding second or third SSDs and "moving" our Saved Games folder to new location. If we ever need to restore the Saved Games path, we need to have this little batch file handy (I am saving it for future for sure.)

Problem has been solved! When I did a fresh install of DCS, and went to Mission Editor, it pointed to my "Document\My Games" folder instead of Saved Games - which I know is default. This was certainly peculiar, but since my "DCS Updater GUI Utility" already had a folder under Saved Games and was working fine (able to clear and re-add paths to DCS and Saved Games folder many times over), I did not suspect it much. Out of desperation, I tried to understand why DCS would not pick that folder, so I searched for default location of Windows 11 Saved Games folder and came across this article (https://www.elevenforum.com/t/move-or-restore-default-location-of-saved-games-folder-in-windows-11.8717/). When I typed shell:SavedGames in file Explorer, it did not do anything! Only after downloading the batch file and running it (which opened up my Saved Games folder with "DCS Updater GUI Utility" in it) that I was able to run Model Viewer without crashing! Model Viewer then came up and I was able to load a model without any issue. I then moved DCS's user folder to the same Saved Games and it loaded my config and liveries, etc. This shows that somehow the Saved Games path in the Windows registry must have been corrupted or otherwise become unusable, which resulted to Model Viewer to ill behave and crash. Obviously, in my opinion Model Viewer should handle this more gracefully and in case it does not find a path to the Saved Games folder, it should print a clear message and terminate.

I am struggling to find the root cause of Model Viewer crashing upon start. I installed the latest DCS (Openbeta 2.9.2.49940) on my non-gaming laptop so I can do some livery development while I'm on extended travel. Installation was fine and Model Viewer started and worked without any issues until I decided I needed more storage space. I cloned my laptop's Windows 11 Pro on a 1TB SSD. While Windows and apps worked just fine, but the Windows admin tools were failing with a weird error message! Not being able to resolve the complex issue, this time, I cloned my Windows 11 Home from my DCS gaming desktop and updated all device drivers on laptop afterwards. Everything went well (including Windows, DCS, Photoshop, all my various programs) with the exception of the Model Viewer, which is crashing upon startup immediately after clicking on it! I have tried the following without any success: repairing, clean-up, brand new reinstall of basic DCS (without any mods), running program in Admin mode, deleting the edModelViewer folder in Saved Games (which came from desktop after cloning), downgrading Intel's graphics driver to two different older versions and upgrading back to the latest one (released just days ago in Jan 2024), deleting temp files related to Model Viewer on AppData/Local folder, resizing screen's resolution, trying the standard non-MT version. Nothing has worked! Right now there is no edModelViewer folder under Saved Games and hence no logs to examine. Windows Event Viewer, however, registers application crashing with the following detail (see below). There is also a crash dump file about 12MB after each incident (attached.) Does anyone have any ideas why this is happening? I don't believe its the program and must be related to the laptop itself, but can't find the culprit. Everything is up-to-date but it keeps crashing. DCS on the other hand, is running smoothly! Any more troubleshooting ideas to try? Thanks! Faulting application name: ModelViewer2.exe, version: 2.9.2.49940, time stamp: 0x657c5d81 Faulting module name: ModelViewer2.exe, version: 2.9.2.49940, time stamp: 0x657c5d81 Exception code: 0xc0000005 Fault offset: 0x000000000003a2f7 Faulting process id: 0x0x3230 Faulting application start time: 0x0x1DA52339B7AC305 Faulting application path: C:\Program Files\Eagle Dynamics\DCS World\bin-mt\ModelViewer2.exe Faulting module path: C:\Program Files\Eagle Dynamics\DCS World\bin-mt\ModelViewer2.exe Report Id: 6a3c6f9d-bc70-45bf-a97e-a7f4ee639dfe Faulting package full name: Faulting package-relative application ID: Fault bucket 1377261530066649997, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: ModelViewer2.exe P2: 2.9.2.49940 P3: 657c5d81 P4: ModelViewer2.exe P5: 2.9.2.49940 P6: 657c5d81 P7: c0000005 P8: 000000000003a2f7 P9: P10: Analysis symbol: Rechecking for solution: 0 Report Id: 6a3c6f9d-bc70-45bf-a97e-a7f4ee639dfe Report Status: 268435456 Hashed bucket: 6eb8648ea4b6acd5f31d0410866f038d Cab Guid: 0 Version=1 EventType=APPCRASH EventTime=133509520655588997 ReportType=2 Consent=1 UploadTime=133509520658401219 ReportStatus=268435456 ReportIdentifier=c6383701-28f4-4bb9-8810-d8734adf1bb6 IntegratorReportIdentifier=6a3c6f9d-bc70-45bf-a97e-a7f4ee639dfe Wow64Host=34404 NsAppName=ModelViewer2.exe AppSessionGuid=00003230-0001-04c1-05c3-7a9b3352da01 TargetAppId=W:0000c0fd784f6861a24ddf45ddf39e03c5350000ffff!00007f1fff8318be8b491547c9ed1fe967362509f874!ModelViewer2.exe TargetAppVer=2023//12//15:14:06:57!21047e!ModelViewer2.exe BootId=4294967295 TargetAsId=323 IsFatal=1 EtwNonCollectReason=1 Response.BucketId=6eb8648ea4b6acd5f31d0410866f038d Response.BucketTable=4 Response.LegacyBucketId=1377261530066649997 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=ModelViewer2.exe Sig[1].Name=Application Version Sig[1].Value=2.9.2.49940 Sig[2].Name=Application Timestamp Sig[2].Value=657c5d81 Sig[3].Name=Fault Module Name Sig[3].Value=ModelViewer2.exe Sig[4].Name=Fault Module Version Sig[4].Value=2.9.2.49940 Sig[5].Name=Fault Module Timestamp Sig[5].Value=657c5d81 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=000000000003a2f7 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.22631.2.0.0.768.101 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=7e5b DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=7e5b553cd5309aef76bbc76186c60f5b DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=8de2 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=8de27bfb7ad4ee7456158d1463f786cb UI[2]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\ModelViewer2.exe LoadedModule[0]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\ModelViewer2.exe LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll LoadedModule[4]=C:\WINDOWS\System32\SHELL32.dll LoadedModule[5]=C:\WINDOWS\System32\msvcp_win.dll LoadedModule[6]=C:\WINDOWS\System32\ucrtbase.dll LoadedModule[7]=C:\WINDOWS\System32\USER32.dll LoadedModule[8]=C:\WINDOWS\System32\win32u.dll LoadedModule[9]=C:\WINDOWS\System32\GDI32.dll LoadedModule[10]=C:\WINDOWS\System32\gdi32full.dll LoadedModule[11]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\GraphicsVista.dll LoadedModule[12]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\renderer.dll LoadedModule[13]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\GraphicsCore.dll LoadedModule[14]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\enlight.dll LoadedModule[15]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\Effects2.dll LoadedModule[16]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\Effects.dll LoadedModule[17]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\PostEffects.dll LoadedModule[18]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\UniModelDesc.dll LoadedModule[19]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\animator.dll LoadedModule[20]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\ImGui.dll LoadedModule[21]=C:\WINDOWS\System32\IMM32.dll LoadedModule[22]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\edObjects.dll LoadedModule[23]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\JConfigurator.dll LoadedModule[24]=C:\WINDOWS\System32\WS2_32.dll LoadedModule[25]=C:\WINDOWS\System32\RPCRT4.dll LoadedModule[26]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\edCore.dll LoadedModule[27]=C:\WINDOWS\System32\ole32.dll LoadedModule[28]=C:\WINDOWS\System32\combase.dll LoadedModule[29]=C:\WINDOWS\System32\SHLWAPI.dll LoadedModule[30]=C:\WINDOWS\System32\msvcrt.dll LoadedModule[31]=C:\WINDOWS\System32\ADVAPI32.dll LoadedModule[32]=C:\WINDOWS\System32\sechost.dll LoadedModule[33]=C:\WINDOWS\System32\bcrypt.dll LoadedModule[34]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\SceneRenderer.dll LoadedModule[35]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\rendererUtils.dll LoadedModule[36]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\edDebugDraw.dll LoadedModule[37]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\NGModel.dll LoadedModule[38]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\libgltf2edm.dll LoadedModule[39]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\lua.dll LoadedModule[40]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\Scene.dll LoadedModule[41]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\Inter.dll LoadedModule[42]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\World.dll LoadedModule[43]=C:\WINDOWS\SYSTEM32\MSVCP140.dll LoadedModule[44]=C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll LoadedModule[45]=C:\WINDOWS\SYSTEM32\VCRUNTIME140_1.dll LoadedModule[46]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\metaShader.dll LoadedModule[47]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\assimp-vc140-mt.dll LoadedModule[48]=C:\WINDOWS\SYSTEM32\D3DCOMPILER_47.dll LoadedModule[49]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\zlib.dll LoadedModule[50]=C:\WINDOWS\SYSTEM32\VERSION.dll LoadedModule[51]=C:\WINDOWS\SYSTEM32\POWRPROF.dll LoadedModule[52]=C:\WINDOWS\SYSTEM32\WINMM.dll LoadedModule[53]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\dbghelp.dll LoadedModule[54]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\freetype.dll LoadedModule[55]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\ModelDesc.dll LoadedModule[56]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll LoadedModule[57]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\dbgcore.DLL LoadedModule[58]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\Qt5Core.dll LoadedModule[59]=C:\WINDOWS\SYSTEM32\USERENV.dll LoadedModule[60]=C:\WINDOWS\SYSTEM32\MPR.dll LoadedModule[61]=C:\WINDOWS\SYSTEM32\NETAPI32.dll LoadedModule[62]=C:\WINDOWS\SYSTEM32\MSVCP140_1.dll LoadedModule[63]=C:\WINDOWS\SYSTEM32\NETUTILS.DLL LoadedModule[64]=C:\WINDOWS\SYSTEM32\SRVCLI.DLL LoadedModule[65]=C:\WINDOWS\SYSTEM32\CRYPTBASE.DLL LoadedModule[66]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\Qt5Widgets.dll LoadedModule[67]=C:\WINDOWS\SYSTEM32\UxTheme.dll LoadedModule[68]=C:\WINDOWS\SYSTEM32\dwmapi.dll LoadedModule[69]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\Qt5Gui.dll LoadedModule[70]=C:\WINDOWS\SYSTEM32\dxgi.dll LoadedModule[71]=C:\WINDOWS\SYSTEM32\d3d11.dll LoadedModule[72]=C:\WINDOWS\SYSTEM32\OPENGL32.dll LoadedModule[73]=C:\WINDOWS\SYSTEM32\GLU32.dll LoadedModule[74]=C:\WINDOWS\SYSTEM32\dxcore.dll LoadedModule[75]=C:\WINDOWS\SYSTEM32\UMPDC.dll LoadedModule[76]=C:\WINDOWS\System32\shcore.dll LoadedModule[77]=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\qwindows.dll LoadedModule[78]=C:\WINDOWS\System32\OLEAUT32.dll LoadedModule[79]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll LoadedModule[80]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll LoadedModule[81]=C:\WINDOWS\System32\bcryptPrimitives.dll LoadedModule[82]=C:\WINDOWS\SYSTEM32\windows.storage.dll LoadedModule[83]=C:\WINDOWS\SYSTEM32\wintypes.dll LoadedModule[84]=C:\WINDOWS\SYSTEM32\profapi.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=22631 OsInfo[3].Key=ubr OsInfo[3].Value=3085 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=1033 OsInfo[7].Key=geoid OsInfo[7].Value=244 OsInfo[8].Key=sku OsInfo[8].Value=101 OsInfo[9].Key=domain OsInfo[9].Value=0 OsInfo[10].Key=prodsuite OsInfo[10].Value=768 OsInfo[11].Key=ntprodtype OsInfo[11].Value=1 OsInfo[12].Key=platid OsInfo[12].Value=10 OsInfo[13].Key=sr OsInfo[13].Value=0 OsInfo[14].Key=tmsi OsInfo[14].Value=222513023 OsInfo[15].Key=osinsty OsInfo[15].Value=1 OsInfo[16].Key=iever OsInfo[16].Value=11.1.22621.0-11.0.1000 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=16125 OsInfo[19].Key=svolsz OsInfo[19].Value=930 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=220506 OsInfo[22].Key=bldtm OsInfo[22].Value=1250 OsInfo[23].Key=bldbrch OsInfo[23].Value=ni_release OsInfo[24].Key=bldchk OsInfo[24].Value=0 OsInfo[25].Key=wpvermaj OsInfo[25].Value=0 OsInfo[26].Key=wpvermin OsInfo[26].Value=0 OsInfo[27].Key=wpbuildmaj OsInfo[27].Value=0 OsInfo[28].Key=wpbuildmin OsInfo[28].Value=0 OsInfo[29].Key=osver OsInfo[29].Value=10.0.22621.3085.amd64fre.ni_release.220506-1250 OsInfo[30].Key=buildflightid OsInfo[30].Value=8E409263-45B4-438D-AD01-6E9674AB032A.1 OsInfo[31].Key=edition OsInfo[31].Value=Core OsInfo[32].Key=ring OsInfo[32].Value=Retail OsInfo[33].Key=expid OsInfo[33].Value=MD:283BAEF,ME:28279A6,FX:12C81471,MD:2A69053,MD:255521A OsInfo[34].Key=fconid OsInfo[34].Value=18299130,0,2,0;19193777,0,2,0;19195493,0,2,0;19638787,0,2,0;23531064,2,2,0;23562335,2,2,0;23563673,2,2,0;32862274,0,2,0;35681102,0,1,0;36803287,0,2,1;36803295,0,2,0;36803303,0,2,1;38277973,0,1,0;38859191,0,2,1;39145991,0,2,0;39146010,0,1,0;39263329,1,2,1;39281392,0,2,0;40025975,0,1,1;40616880,0,1,1;40883769,0,1,1;40981503,0,1,1;41135193,0,1,1;41137130,0,1,0;41342175,0,1,1;41655236,0,2,0;41772259,0,2,1;41799415,0,2,1;42052423,0,2,0;42105254,0,2,0;43133808,1,2,1;43169616,0,1,0;43203978,0,2,1;43572857,0,2,1;43772553,0,1,0;43844371,0,1,1;43978769,0,1,1;43998261,0,2,1;44325080,0,1,1;44470355,0,1,0;44521793,0,1,0;44552141,0,1,0;44776738,0,2,0;45113694,0,2,1;45185354,0,2,0;45732051,0,2,0;45786062,0,2,1;45796396,0,2,0;45949789,0,0,0;45952594,0,2,0;45952872,0,2,0;45991456,0,1,1;45999439,0,0,0;46094352,0,2,1;46251949,0,2,1;46551074,0,1,1;46557400,0,1,1;46604216,0,2,1;46619189,0,2,1;46717502,0,2,0;47526873,1,2,1;47557358,0,2,1;48057519,0,2,1 OsInfo[35].Key=containerid OsInfo[36].Key=containertype OsInfo[37].Key=edu OsInfo[37].Value=0 OsInfo[38].Key=servicinginprogress OsInfo[38].Value=0 OsInfo[39].Key=featureupdatependingreboot OsInfo[39].Value=0 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=DCS AppPath=C:\Program Files\Eagle Dynamics\DCS World\bin-mt\ModelViewer2.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=1B31709379713A6BDB8F25A3B38567D5 MetadataHash=-42217089 ModelViewer2.exe.7572.dmp

This was a major source of frustration for me for a long time. Changing the suggested values as part of default.lua file had not affect for me. What did work, however, was to reduce the time that the commands were applied when they were input from Hotas. I have a Logitech X52 and I do all my mappings outside DCS using it's programming tool. Instead of applying the keyboard inputs for "-" and "=" set as Buttons, I set up Advanced Commands (which controls how long various key inputs are applied when certain buttons/controls are pressed on the Hotas.) After reducing the time delay all the way down to 0.01msec that I was able to have a fine control over the elevation of antenna. Problem solved. So, if your Hotas allows you to control the time duration applied for a keybinding, then this maybe a more effective solution.

In that case, I am happy with the outcome. Thanks for clarifying this.

Thank you both for commenting. I just tried this and it worked. However, this is news to me! For the past several years, I have been turning the smoke on and off by pressing the weapon release button while having the Selective Jettison on Off position. This was obviously easier since we all have the weapon release button mapped to our HOTAS but not everyone has the Jettison button mapped. If in the real world, pushing the Jettison button controls the smoke, then let it be and I am fine with that, otherwise I would rather see the procedure revert to how it was. Edit: How come this change of behavior was never documented in the change logs of the releases in the first place?

It appears generating smokes in 2.9 release no longer works! I tried with master arm on, wingtip stores selected, jettison position in off position, and nothing happens when I press the drop weapon button.

Thanks, that worked. I was away for a couple of months. Once I returned, I upgraded DCS to 2.9.1.x and loaded a saved mission with Su-30 doing AAR and all I got was silence! No problem, the more realistic the better.

I am trying to air-to-air refuel post 2.9 release and tanker no longer responds! I am fairly sure this all worked prior to that release. Could someone please confirm this? Thanks!

Appreciate all the work yourself and others are putting into this. If I had any experience in mod development, I would have thrown my hat in the ring long time ago. For now, I'll be patient until the EFM model along with other improvements are ready to be released in a future update. Thanks!

May I ask how far in the development are you before you release the next version? It's already been many months since the current version came out. If it is too far out, is it possible to get an interim release sooner with some of the smaller improvements such as moving canards, conformance to other modules for left/right mouse click operation, etc.? We can then get the main flight model improvement in a follow on release. Thanks.

I did look at this page more than once but missed the link in that post! Thank you so very much. It saved me a ton of time.

Found the older B version under "VSN_F4 v2.7.10.02 FC3 F4 EFM" which does not have the updated rivets and markings as the newly released C/D version. So question stands!

Hi, I am trying to make a skin for VSN's F-4B/C Mod but all I can find under Textures directory of the mod are the DDS files. I can't seem to find where the layered Photoshop version of the main file 'VSN_F4E_1' is! I have looked at VSN's download site and searched this forum as well as under ED's User Files but no luck. Any links or pointers are appreciated.

I did spend sometime and removed the pylon prints and it came out okay. It should do until such time that HB will update their texture files for 95-GR.

First off, many thanks to HB for making the effort and allowing drop tank pylons to be removable. Flying an early -A Tomcat would not feel "right" with those pylons. Now the question is that would HB release an update to the texture files that do not have the pylon prints baked in the textures? Removing them is not exactly trivial, but doable after spending some considerable amount of time to blend seamlessly. Before doing that for my skins, I wanted to see what HB's plans are. Thanks.

Speaking of small but important things, I wonder why you chose to implement different mouse clicks for the cockpit. In every other clickable module, left mouse button turns a knob CCW and right button CW. Also left button turns off a switch (down position), and right button turn on a switch (up position). In Su-30, we see mostly opposite, but sometimes even that is not consistent. For example, for Master ARM, left mouse button toggles the switch and right mouse button does nothing! Other knobs and switches are reverse of what should be, left button is CW and right button is CCW. That doesn't make sense. Why not be consistent and match every other module so our memory muscle to handle the cockpit does not have to be retrained for no special reason? I brought this issue up almost exactly a year ago but I guess it went unnoticed. Obviously, I am nitpicking out of affection for this module that I see myself spending a lot of time in. Hope to see any attention to these issues. About the Comm Menu shortcut I mentioned in the post above, modules such as F-14 that have two radios with two different shortcuts still allow "\" to operate the Comm Menu. I really hope Su-30 would follow suit. Many thanks!

Thank you! Speaking of small things that would add a good amount of user satisfaction is to use "\" for Radio 1 instead of the current "RShift \". I understand you have touched upon this before, but just to provide an example of the impact, every command under Comm Menu that is used in VoiceAttack needs to be duplicated for the Su-30. For instance, for calling Tanker Menu or AWACS, we need to say "Su 30 AWACS", etc. This adds to the burden of maintaining a fair amount of VoiceAttack commands but also keeping in mind, in the midst of intense missions, that I need to add "Su 30" to my voice commands, a distraction that I prefer not to have.

Would it be possible to add keybindings for external NAV light %, perhaps two actions to switch positions CCW and CW? Under VR, it's really a stretch for neck to pin point a small area and click multiple times for example to turn the lights on and off. Small improvements such as this elevates this fantastic module to greater heights for me

Does night vision goggle work in this module? "RShift + H" which is listed in the commands does nothing! Note that I have not attached the Sura Helmet Mounted Sight for NVG to work. Thanks.

For the ingame option you mentioned, of course I looked at Setting -> Special -> Flanker Ex section prior to asking but did not see any option for English cockpit. From the screenshots in this forum I can see the MFD in English and that's wonderful. Would you, or others, please educate me exactly how to enable this feature? I feel I'm just one step away from a great SU-30.

Thank you freebirddz. They both worked. Having said that, what is the rational for changing the key bind for Comm Menu that is "\" in every other module in DCS? Why deviate and not follow common defaults for this module? It's like changing the gear command from "g" to "RShift + g". It will work but it is not optimum. Now, I have to add a different command to VoiceAttack for Su-30 to access Comm Menu. It's unnecessary. As for attaching Sura, doesn't it make sense to make that default in the mission editor? This is still an awesome module and I'm having a ton of fun with it. My only problem is the Russian language in the MFDs. I cannot effectively use all that information. I have set Cockpit_LANG='ENG' in config.lua file but apparently that's only for HUD.

I'm having trouble opening the Communication Menu!! Is this an issue on my part or others are having difficulty too? Adding to this is the ACM helmet mounted sight. It no longer works in the new release!

Sure. In fact it was one the early liveries that was released months ago....https://www.digitalcombatsimulator.com/en/files/3320065/ See: https://forum.dcs.world/topic/247098-dcs-su-30mmk-mod/page/29/#comment-4899078

Automan, you are my hero! That was it! It worked like a charm. Thank you so much for taking time to read about my issue and comment. I don't know how to thank you enough. Interestingly, I had tried both the first and last plugins on the site (both built in May 2022), but neither worked. Even though I was suspicious of the plugin as the culprit, I just couldn't see how there could be such a major issue with them and still be posted as the official releases.