JAPman

Hinds are as strong as Apaches when made into enemies? If you inadvertently make an Apache appear in the mission generator, the Hellfire will pour down like a demon and destroy the Red Army.

Checking Static Template, there is only a Nazi radar base and a V1 site. Looks like revisionist space... I see that The Fighter Collection's Flying Legends has moved from Duxford to Church Fenton, after being discontinued in Corona.

Ah, surely this may be a crisis of Christian civilization as advertised. East Asian Buddhists are also worried. The Channel Map is probably not continuous in space with the Normandy Map, when the US was adhering to Monroeism before Pearl Harbor.

This map is modest in its historical architecture and churches, and looks somewhat bleak, like the human world today. -- edit Church of St Mary the Virgin, in Ashford Sorry, I may be a little biased. As others have said, it seems difficult to find POI's at 300 mph, maybe I should try flying on I-16.

I'm not that familiar with military history, so I've learned a few things. After taking off from Detling with my unfamiliar Spitfire takeoff training, I strolled around following the gentle hills of England, which are difficult to identify only at low altitudes, on the newly introduced Channel map, and found what appeared to be a very large radio tower for 1940, west of Canterbury. Dunkirk, Kent https://en.wikipedia.org/wiki/Dunkirk,_Kent At the time of the Battle of Britain, a Jewish-French woman mystic (- 1944 England), whom I admire, wrote of watching Hitler abandon his invasion of England from continental Europe, as if a holy power had pushed back the Nazi advance. At the time, Britain had the world's most advanced radar air defense network in place, and it is said that because of this, Britain was able to effectively intercept incoming German planes. Chain Home https://en.wikipedia.org/wiki/Chain_Home Spitfire intercepting Messerschmitts in front of the White Cliffs of Dover https://www.youtube.com/watch?v=kBm86lrCq2c Without this world's most advanced radar air defense network, perhaps the British would have succumbed to the Nazis, the FDR administration in the U.S. would have been driven into a corner by domestic pro-Hitler forces in an anti-communist domino, the Empire of Japan would not have needed Pearl Harbor in 1941, and the Axis alliance would not have lost. As a Japanese, I am quite deeply moved by this story.

I preferred the La-7 in IL-2/1946 and was impressed by the automatic deployment of the wing leading edge flaps with a wind noise before stalling.

My X56 stick became unresponsive after being left untouched for a while. This is a symptom generally attributed to inferior liquid capacitors used in cheap consumer electronics products. Up until around X52, electronic components were made in Japan as a continuation of the Cold War period, but X56 may have been designed at the wrong time. Because something is made in Japan, it does not necessarily mean that everything is safe. The Omron and Alps tact switches used in Saitek devices are not durable enough for gaming devices. When they become unresponsive, you have to check the model number and replace parts regularly.

In the case of using the FFB stick with Instant trim, when the trim button is pressed, the cyclic simply transitions to the center at that angle, which is easy to understand. At the time of the release of the 32-bit DCS-BS ver1.0.0, there was no other option but Instant trim. This is effectively a configuration for the G940, which Logitech developed simultaneously for the BS, and which is difficult to use with common spring sticks. Central Position Trimmer mode for spring centered sticks was added in ver1.0.1. The trouble for me is setting up the pedals. Basically the same as for sticks, owners of FFB pedals, which are probably a minuscule number, should choose Instant Trim, and Central Position Trimmer mode for spring-centered pedals. If you have a pedal with a damper and no spring, or if you are like me and use the rotary on the throttle as the pedal axis, select Do not trim. I came to this understanding through trial and error. In the trim mode of the stick, there is an item Without spring and FFB. I have not yet tried it to see what the behavior would be if I remove the spring from my stick and use only the damper. Hind is good to be able to adjust trim with HAT.

What about disassembling and dusting the wiring and electronic circuit board using a brush or similar?　I have not tried this yet, but the ghosting input did not occur in the early days of my purchase. The stick promptly died, though. It was a failure as far as Logitech product quality.

This is amateur guesswork, but isn't it possible that this is the same function as the stick shaker, to let the pilot know that the airbrakes are deploying?　I am a fidgety person and sometimes forget to close the airbrakes. The Su-25, which descends rapidly with the airbrakes deployed when dropping unguided bombs, will have these on the wingtips that do not deviate from the aircraft's center of gravity to avoid deflecting its path due to brake deployment The Su-25 appears to be a very particular aircraft design in this regard. The FSX F-18C was interesting in that the deployment of the airbrakes raises the nose of the plane so that the back is pulled backward. I really like the centerless SWFFB2, as it allows for easy, subtle aircraft control and gives the illusion of improved formation flying.

Oh, my bad; the PBR file was already there. This is good. Sometimes the server is too heavy to find them. The textures were applied by placing them in the mod folder of JSGME and activating them. Su-25-RoughMet https://www.digitalcombatsimulator.com/en/files/3322005/

I did buy the Su-25 separately and properly... livery = { {"su25-fuz-center", 0, "SU25-PAINT1-RUS-DEF-01", true}, {"su25-wings", 0, "SU25-PAINT2-RUS-DEF-01", true}, {"Su-25-flap-details", 0, "SU25-PAINT2bis-RUS-DEF-01", true}, {"su25-fuz-tail & fin", 0, "SU25-PAINT3-RUS-DEF-01", true}, {"su25-tail & stab", 0, "SU25-PAINT4-RUS-DEF-01", true}, {"su25-brake-L", 0, "SU25-PAINT5-L-RUS-DEF-01", true}, {"su-25-brake-R", 0, "SU25-PAINT5-R-RUS-DEF-01", true}, {"su25-fuz-nose", 0, "SU25-PAINT6-RUS-DEF-01", true}, {"su-25-pitot+", 0, "SU25-PAINT6B-RUS-DEF-01", true}, {"su25-gear-metal", 0, "SU25-PAINT7-RUS-DEF-01", true}, {"Su-25-gear-steel", 0, "SU25-PAINT7-RUS-DEF-01", true}, {"Su-25-gear-rubber", 0, "SU25-PAINT7-RUS-DEF-01", true}, {"su-25-fuz-details", 0, "SU25-fuz-dets-RUS-DEF-01", true}, {"SU-25-PILON", 0, "Su25-PILON-PAINT-RUS-DEF-01", true}, {"SU-25-PILON_2", 0, "Su25-PILON-2-RUS-DEF-01", true}, {"Su-25-numbers-1", 0, "rus-code-numbers-ver2-W", true}, } name = "field camo scheme #1 (native)" name_ru = "полевой камуфляж - схема 1" countries = { "RUS", "SUN" }

I assign the cockpit zoom to the slider axis of the input device and set the zoom to normal when the slider is full. The cockpit FOV is adjusted using CameraViewAngleLimits in "Config/View/Server.lua". The MaxFOV of CameraViewAngleLimits is a batch setting for all FC3 aircraft, but for example, MiG-29, Su-27, and Su-33 require separate settings. So, in order to set MaxFOV for each aircraft, I rewrote Server.lua a little. Change "140.000000" in the line commented "-- Cockpit MIN/MAX FOV" for each aircraft. This file should be placed in the "Saved Games/DCS(.openbeta)/Config/View" folder. I think this is a basic adjustment method. Translated with www.DeepL.com/Translator (free version) -- View scripts -- Copyright (C) 2004, Eagle Dynamics. DisableCombatViews = false -- F5 & Ctrl-F5 ExternalObjectsLockDistance = 10000.0 ShowTargetInfo = false CameraTerrainRestriction = true hAngleCustomDefault = 0.0 vAngleCustomDefault = -8.0 vAngleCustomMin = -90.0 vAngleCustomMax = 90.0 UseGreenieBoardLandingDataHistory = true -- For Carrier Air Wing Briefing Room UseKillBoardDataHistory = true --reformatted per-unit data to be mod system friendly --this file is no longer should be edited for adding new flyable aircraft , DCS automatically check core database (i.e. where you define your aircraft in aircraft table just define ViewSettings and SnapViews tables) function default_fighter_player(t) local res = { CameraViewAngleLimits = {20.000000,140.000000}, CameraAngleRestriction = {false ,90.000000,0.500000}, EyePoint = {0.05 ,0.000000 ,0.000000}, limits_6DOF = {x = {-0.050000,0.4500000},y ={-0.300000,0.100000},z = {-0.220000,0.220000},roll = 90.000000}, Allow360rotation = false, CameraAngleLimits = {200,-80.000000,110.000000}, ShoulderSize = 0.2, -- move body when azimuth value more then 90 degrees } if t then for i,o in pairs(t) do res[i] = o end end return res end function fulcrum() return { Cockpit = { default_fighter_player({CockpitLocalPoint = {4.71,1.28,0.000000}, CameraViewAngleLimits = {20.000000,140.000000}}),-- Cockpit MIN/MAX FOV }, Chase = { LocalPoint = {1.220000,3.750000,0.000000}, AnglesDefault = {180.000000,-8.000000}, }, -- Chase Arcade = { LocalPoint = {-15.080000,6.350000,0.000000}, AnglesDefault = {0.000000,-8.000000}, }, -- Arcade } end ViewSettings = {} ViewSettings["A-10A"] = { Cockpit = { [1] = default_fighter_player({CockpitLocalPoint = {4.300000,1.282000,0.000000}, CameraViewAngleLimits = {20.000000,140.000000},-- Cockpit MIN/MAX FOV EyePoint = {0.000000,0.000000,0.000000}, limits_6DOF = {x = {-0.050000,0.600000}, y = {-0.300000,0.100000}, z = {-0.250000,0.250000}, roll = 90.000000}}), }, -- Cockpit Chase = { LocalPoint = {0.600000,3.682000,0.000000}, AnglesDefault = {180.000000,-8.000000}, }, -- Chase Arcade = { LocalPoint = {-27.000000,12.000000,0.000000}, AnglesDefault = {0.000000,-12.000000}, }, -- Arcade } ViewSettings["F-15C"] = { Cockpit = { [1] = default_fighter_player({CockpitLocalPoint = {6.210000,1.204000,0.000000},-- player slot 1 CameraViewAngleLimits = {20.000000,140.000000}}),-- Cockpit MIN/MAX FOV }, -- Cockpit Chase = { LocalPoint = {2.510000,3.604000,0.000000}, AnglesDefault = {180.000000,-8.000000}, }, -- Chase Arcade = { LocalPoint = {-13.790000,6.204000,0.000000}, AnglesDefault = {0.000000,-8.000000}, }, -- Arcade } ViewSettings["MiG-29A"] = fulcrum() ViewSettings["MiG-29G"] = fulcrum() ViewSettings["MiG-29S"] = fulcrum() ViewSettings["Su-25"] = { Cockpit = { [1] = default_fighter_player({CockpitLocalPoint = {3.352000,0.506000,0.000000},-- player slot 1 CameraViewAngleLimits = {20.000000,140.000000}}),-- Cockpit MIN/MAX FOV }, -- Cockpit Chase = { LocalPoint = {-0.348000,2.906000,0.000000}, AnglesDefault = {180.000000,-8.000000}, }, -- Chase Arcade = { LocalPoint = {-16.648001,5.506000,0.000000}, AnglesDefault = {0.000000,-8.000000}, }, -- Arcade } ViewSettings["Su-25T"] = { Cockpit = { [1] = default_fighter_player({CockpitLocalPoint = {3.406000,0.466000,0.000000},-- player slot 1 CameraViewAngleLimits = {20.000000,140.000000}}),-- Cockpit MIN/MAX FOV }, -- Cockpit Chase = { LocalPoint = {-0.294000,2.866000,0.000000}, AnglesDefault = {180.000000,-8.000000}, }, -- Chase Arcade = { LocalPoint = {-16.594000,5.466000,0.000000}, AnglesDefault = {0.000000,-8.000000}, }, -- Arcade } ViewSettings["Su-27"] = { Cockpit = { [1] = default_fighter_player({CockpitLocalPoint = {7.959000,1.419000,0.000000},-- player slot 1 CameraViewAngleLimits = {20.000000,140.000000}}),-- Cockpit MIN/MAX FOV }, -- Cockpit Chase = { LocalPoint = {4.259000,3.819000,0.000000}, AnglesDefault = {180.000000,-8.000000}, }, -- Chase Arcade = { LocalPoint = {-12.041000,6.419000,0.000000}, AnglesDefault = {0.000000,-8.000000}, }, -- Arcade } ViewSettings["Su-33"] = { Cockpit = { [1] = default_fighter_player({CockpitLocalPoint = {7.959000,1.419000,0.000000},-- player slot 1 CameraViewAngleLimits = {20.000000,140.000000}}),-- Cockpit MIN/MAX FOV }, -- Cockpit Chase = { LocalPoint = {4.259000,3.819000,0.000000}, AnglesDefault = {180.000000,-8.000000}, }, -- Chase Arcade = { LocalPoint = {-12.041000,6.419000,0.000000}, AnglesDefault = {0.000000,-8.000000}, }, -- Arcade } Server.lua

I too think some caution should be exercised about the possibility of overbalancing the game at the expense of the reality of the simulator.

The SWFFB2 was a stick for the Zero Fighter when MS released the CFS2 for the Pacific Theater, and the seemingly insignificant grip sensor indicates the high quality of the product. I gave up on the method of blocking the sensor because if I was not careful, the stick would start up with a violent noise the moment Windows started up. The level flight AP button, a standard feature on Russian fighter grips, is stable in high-altitude cruising.

With 2.8.1, the Hind lightweight mod I created seems to have lost its effect. is it processing efficiency, as the ED announcement said? Thankfully BS3 is also lightweight, though I've been experiencing display bugs with mirrors since 2.8.0. I hear there is such a thing as a Windows 11 + HDR capable display these days. It seems to take a little more time until it becomes popular. https://www.digitalcombatsimulator.com/en/files/3326699/

There are an unexpectedly large number of objects in the quick-start short-range free-flight mission.

I forgot to leave the Windows paging file turned off to suppress the Prepar3Dv5 stuttering, and my PC's memory flooded and was awfully unstable. On a different topic, if the city near the airfield is omitted, I get confused when I am flying in VFR relying on a static map while asking ATC for a heading. It's not just the Syria map that has the city area cleared in places. It's unavoidable due to map data capacity.

The exe file now has an icon. Reloading textures is instantaneous and a necessity for repainting. Thank you. b2.8.1 has no problem when launching ModelViewer2.exe directly. However, in a multiple install with b2.7.18, if I specify ModelViewer2.exe in "Always use this app to open .edm files" and open the .edm file, it refers to the b2.7.18 folder. Is this an old bug? Even starting from GUI Utility results in an error. --------- edit ----------- When I did a multiple install, I solved the problem by temporarily deleting all ModelViewer2.exe from the other version and specifying a new one with "Always use this app to open .edm files". It seems to be a Windows problem. Sorry about that.

Correction. The above addition to Views.lua in L-39 seems to remove the MAX FOV limitation for now, but it is difficult to set it the way you want. If I export SnapViews.lua to Saved Games\DCS\Config\View with RAlt+num0 and change viewAngle and vAngle in [13](default view) of L-39C/ZA, those settings seem to live. It is a bit complicated.

local playerSnapViews = { [13] = head_pos_default({ viewAngle = 90.000000, }),--default view } DCS World\Mods\aircraft\L-39C\Views.lua I finally figured it out! Using TrackIR Assign device rotary to Zoom Axis and specify slider.

In the age of 4K monitors, 4Kx4K textures have become the standard, and with normal maps and PBR textures attached, the memory load will increase and become heavier. If the image is displayed at MIP level 2 without zooming in, then 2Kx2K textures may be sufficient. The BC7 DDS was convenient to edit with paint.net.

I was taught that way by a joking instructor in FSX C172 training. The little ball of VC can't look away from the front, and to get lateral G's with sims, I need a hydraulic seat, but I'm poor. I say this just to make a suggestion, since it doesn't seem that difficult to implement.

Just use the data that the VC slip ball display is getting and display it on the controls indicator. It is difficult to make beautiful coordination turns.

As a suggestion, since we cannot physically feel the lateral Gs of a sideslip, I would like to see a magnified view of the sideslip ball as shown in the image to compensate visually by means of an indicator.