Jump to content

Shimakaze514

Members
  • Posts

    9
  • Joined

  • Last visited

About Shimakaze514

  • Birthday 03/02/1873

Personal Information

  • Flight Simulators
    DCS MSFS2020 P3Dv5
  • Location
    Osaka
  • Interests
    DEBUGGING

Recent Profile Visitors

185 profile views
  1. Still no progress on IC-friendly method to disable the black background of MFDs, can someone help? @BIGNEWY
  2. A few updates ago(after some version in 2.8.x) , AGM-65 lost its ability of tracking fast-moving targets such as helicopters, while functioning as intended when tracking the slow ones. The Mavs can definately see the target, completely able to track it(target is within the seeker FoV and G limit) , having enough energy to hit, but it just 'refuses' to track it. That disabled the ability of fixed-wing aircraft to attack helicopters using any Mavericks. I have tested out all variant, including TV, IR, and laser guided. It seemed that the problem is at the weapon scheme: I've checked "DCS World OpenBeta\CoreMods\aircraft\AircraftWeaponPack\agm65_family.lua", found that max G of the missile is 16, the seeker Fi shows he can track targets 180° in the front hemisphere, and the 'Omviz' value is 99.9, which indicates a very big LOS velocity, in conclusion, it seemed that Mav's lua file won't stop it to track a fast-moving target. So I doubt it's the scheme, all Mavs share 2 schemes, agm65 or agm65e, now both of them are 'brocken' in some ways. If anyone wants to test it out, try shooting at a heli moving at ~100knots. It would be more obvious if you can ask a friend flying a heli and start accelerating from hover as you fired a maverick at him. At first I thought only the IR and TV seekers are broken. Recently I checked the Laser seeker, it turns out to be no joy either. The Maverick is flying like it lost any purpose, when the heli increase it's speed above threshold, the Mav won't control its rudders and allowing itself to fall.
  3. Temporary fix: Edit this file in line 46, change HUD_only_back.material = MakeMaterial("",{0,0,0,255}) into HUD_only_back.material = MakeMaterial("",{0,0,0,0}) so that the background material will be transparent special reminder: uncomment line 51 will not cause any visible change.null edited file and preview screenshot are attached below IC unfriendly With regard to that players have different preferences on MFD background (some thought transparent background caused readability of MFD content to reduce, others thougt black background will block cockpit vision), instead of limit the option with IC, it might be a good idea to make a option under "settings - special - <aircraft>" that allow player to choose whether they want a transparent MFD background or not.MPD_common_bake_page.luanull
  4. Temporary fix: Edit this file in line 46, change HUD_only_back.material = MakeMaterial("",{0,0,0,255}) into HUD_only_back.material = MakeMaterial("",{0,0,0,0}) so that the background material will be transparent special reminder: uncomment line 51 will not cause any visible change.null edited file and preview screenshot are attached below IC unfriendly With regard to that players have different preferences on MFD background (some thought transparent background caused readability of MFD content to reduce, others thougt black background will block cockpit vision), instead of limit the option with IC, it might be a good idea to make a option under "settings - special - <aircraft>" that allow player to choose whether they want a transparent MFD background or not. MPD_common_bake_page - edited.lua
  5. MFD export effect before 2.8.3.37854.1 Open Beta update: After the update: My MonitorSetup: _ = function(p) return p; end; name = _('3440MFD+'); Description = '3440*1440' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } LEFT_MFCD = { x = 790; y = 410; width = 620; height = 620; } RIGHT_MFCD = { x = 2030; y = 410; width = 620; height = 620; } --[[ CENTER_MFCD = { x = 1565; y = 100; width = 310; height = 310; } ]] JF17_LEFT_MFCD = { x = 350; y = 0; width = 620; height = 930; } JF17_CENTER_MFCD = { x = 2820; y = 0; width = 620; height = 930; } F14_TID = { x = 2030; y = 410; width = 620; height = 620; } GU_MAIN_VIEWPORT = Viewports.Center Previously I can see thru the MFDs on my screen and get a very clean view on the outside while don't have to lower my head and zoom in to see the MFDs, this can be a great help to enjoy flying and operating avionics at the same time, since you can choose a position you like to place the MFDs and read the information on them more confortably. Its for the same reason that some people buy a external screen and export MFD on it. building a monitor setup on the screen is just like building a cabin with many external screen at home, the only difference is one is virual and cheaper, the other is solid and obviously more costy. This should not be canceled just because of "simulation", it's player's freedom to display their MFDs wherever they like without obstucting the main view.
  6. MFD export effect before 2.8.3.37854.1 Open Beta update: After the update: My MonitorSetup: _ = function(p) return p; end; name = _('3440MFD+'); Description = '3440*1440' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } LEFT_MFCD = { x = 790; y = 410; width = 620; height = 620; } RIGHT_MFCD = { x = 2030; y = 410; width = 620; height = 620; } --[[ CENTER_MFCD = { x = 1565; y = 100; width = 310; height = 310; } ]] JF17_LEFT_MFCD = { x = 350; y = 0; width = 620; height = 930; } JF17_CENTER_MFCD = { x = 2820; y = 0; width = 620; height = 930; } F14_TID = { x = 2030; y = 410; width = 620; height = 620; } GU_MAIN_VIEWPORT = Viewports.Center Previously I can see thru the MFDs on my screen and get a very clean view on the outside while don't have to lower my head and zoom in to see the MFDs, this can be a great help to enjoy flying and operating avionics at the same time, since you can choose a position you like to place the MFDs and read the information on them more confortably. Its for the same reason that some people buy a external screen and export MFD on it. building a monitor setup on the screen is just like building a cabin with many external screen at home, the only difference is one is virual and cheaper, the other is solid and obviously more costy. This should not be canceled just because of "simulation", it's player's freedom to display their MFDs wherever they like without obstucting the main view.
×
×
  • Create New...