Jump to content

mkiii

Members
  • Posts

    679
  • Joined

  • Last visited

Everything posted by mkiii

  1. As the title suggests, since Release version 1.58, I have had a darker shaded area appear across the top of the screen when fully zoomed out. It appears to be the same shade of transparent grey that the harrier HUD glass uses in it's darker top glass section & occupies roughly 1/4 of the total screen area. This appears in 2 of the aircraft that have a helmet visor option, EG AV8, M2000, but not the Mig-21, which has the effect filling all screens properly, regardless of FOV. When the visor is enabled in the AV8/M2000, the dark area slides down to the occupy the middle 1/3 of the screen. The visor area is obviously not far enough off screen to begin with, and not big enough to fill the screen completely when it is operated.
  2. As far as the canopy goes, has anyone else noticed the crackles effect is way too low res? Compared to the M2000 for example, even though the textures are the same size.
  3. It's surprising how few people go for the SU-25T considering that it is free. It's quite a blast launching Vikhr after vikhr missile at a tank column. The only thing against it imo, is the non clickable cockpit, but a decent HOTAS or extra keyboard/MFD can negate that problem. Yeah, the a-10 is great, but it's amost too easy. Harrier is fun - but lots of stuff missing. If you want a real challenge, try the SU-25A...
  4. This sometimes happens to me after updates. Usually, deleting (backup first) the Saved Games\DCS\MissionEditor folder, & then letting DCS recreate it solves the problem. I then copy my old logbook.lua & settings.lua back, & check it works as before.
  5. To turn off cockpit MFDs but still have them exported to other monitors:- Look in the file C:\Program Files\Eagle Dynamics\DCS World\Scripts\Aircrafts\_Common\Cockpit\ViewportHandling.lua for the Line (should be around line 81):- purposes = {render_purpose.GENERAL, And comment it out thus:- purposes = {--render_purpose.GENERAL, Don't forget that to export the displays, in addition to having the MFDs set up in the monitor config, you also need to enable keystrokes in-game to turn them on, unlike other aircraft (apart from the M2000). These keystrokes are not set up by default. I use a shifted command on the F-16 MFD gain button on each MFD to set this. Alternatively, something like ALT+z & Alt+x works ok.
  6. AFAIK it just means PRimary and OPtion (note. PR not RP). I havent noticed any difference - neither seems to work for me.
  7. Having the Cougars preset saves a lot of time, but it would be helpful if you could assign ANY new commands to them in the control setup GUI as a default, as you can in other aircraft. At the moment they cannot be assigned with anything other than MFCD commands. Allowing this, especially with shifted/Modified commands gives us a lot more flexibility.
  8. Check out the control settings. There are 2 commands that you need to assign keystrokes to in order to enable left or right off export. A bit like the m2000. I have mine set to ctrl+a and ctrl+d.
  9. Is it not worth making this thread sticky?
  10. There are brakes!? :)
  11. It sounds like your "Center" viewport is covering both monitors. You need to make sure the GUI resolution setting is equal to the combined width/height of your monitors, but in the .lua file, you need to define Viewports that equal the size of each screen (or screens) that you intend to display to, with Center defining the main 3d screen position & size - note that this can cover multiple monitors. As in the example above, you also define the position and size of the MFD exports. There are lots of threads covering this. Re Exporting: Strangely, I booted her up again today and the MFDs appeared on my 4th monitor without having to add a keystroke. So all good. However, the beta is a bit badly behaved for me, and won't let me edit kestrokes from the GUI - black screen = result, meaning I have to quit via task manager. Not sure if that is just on the Harrier because I don't want to wipe any existing setups on other modules. I can still edit them in game so no biggie.
  12. This Line is commented out in AV8BNA/Cockpit/MPCD/Indicator/MPCDR_init.lua try_find_assigned_viewport("RIGHT_MFCD") The same for the Left one. I tried uncommenting them, but nothing was exported. At least it looks like they "should" work the same was as the A10 at some point.
  13. I can certainly attest that a lightly loaded combat aircraft (Tornado in my experience) will quite happily bog itself in up to the axles if it leaves the taxyway, even with just one oleo. Why would anyone think otherwise? Old Soviet aircraft may be designed to cope with rough strips, but not turf laid over soil. Even something as light as a DH Chipmunk, operating from a (rolled) grass strip, has bogged in (and nosed over) in my experience when it deviated from the prepared grass area.
  14. An experiment: For those that find the Spit a bit too lively on its gear, have a go with these FMOptions.lua settings. They adjust the springiness & so on of the gear. Modified sections are commented "--Original "and are set to represent the Maximum / Easiest settings - try them, then adjust them one at a time back towards the original settings as shown, to see which one has the most effect. With these initial settings, you will find that the thing is fairly docile on the ground, and tracks pretty straight, and will not bounce too high on touchdown. Personally (and it is just an opinion), I believe the tail strut has too much bounce.. and to some extent, the main struts too. Note, RL A/C that are not perfect modern restored examples, unless fresh out of the factory, would not be as lively as I suspect this one is trying to represent. This is the opinion of Groundcrew rather than pilot btw. As a comparison, you might want to compare this lua to the other tail draggeers, and note the differences. For best results create a folder in Generic Mod Enabler or similar, so you can more easily undo any changes prior to any updates. The file is DCS World\Mods\aircraft\SpitfireLFMkIX\FMOptions.lua <<<< Note Release version only. tailWheelStaticFricK = 0.6 tailWheelSideFricK = 0.5 tailWheelRollFricK = 0.025 tailWheelGlideFricK = 0.54 tailWheelMOI = 0.5 mainWheelStaticFricK = 0.71 mainWheelSideFricK = 0.73*.8 mainWheelRollFricK = 0.022 mainWheelGlideFricK = 0.69 mainWheelBrakeMomentMax = 0.33 * 8000.0 mainWheelMOI = 3.6 tailGearYawDamperK = 36.0 tailGearAxleFricM0s = 80.0 tailGearAxleFricM0f = 35.0 -- Original 11.0 tailGearAxleFricVs = 0.2 tailGearAxleFricVf = 4.0 tailGearStockLength = 0.1 tailGearSpringForceFactor = 11000000 .-- Original 17000000 tailGearSpringForceFactorRate = 3 tailGearStaticForce = 30000 -- Original 3000 tailGearReduceLength = 0.08 tailGearDirectDamperForceFactor = 3000.0 tailGearBackDamperForceFactor = 84000.0 tailGearDamageLengthLim = 0.15 mainGearSpringForceFactor = 3.2 * 1000000 -- Original 6.2 * 1000000 mainGearSpringForceFactorRate = 3.3 mainGearStaticForce = 3300.0 mainGearReduceLength = 0.14 mainGearDirectDamperForceFactor = 2000.0 mainGearBackDamperForceFactor = 100000 -- Original 10000.0 mainGearDamageLengthLim = 0.17 skew_w_wingK = 0.7 skew_w_tailK = 1 governorRegK = 0.0003 governorVelK = 0.0035 governorDamperK = 0.00002 governorNscale = 0.0 governorNc1 = 160.0 governorNc2 = 320.0 governorNc3 = 0.003 transversalK = 1.0 fuselageMyDampK = 0.6*0.0 fuselageMzDampK = 0.19*0.7 wingMzDampK = 0.43*0.7 stabSkewK = 0.9 aileronTrimTab = -0.045 elevatorTrimTab = 0.0 rudderTrimTab = 0.0 contactPosShiftK = 0.0 tailShadowPower = 10 tailShadowK = 0.75 tailShadowSpread = 23 damperShadowK = 0.6 wingShakeFilterK = 0.7 wingShakeFilterLim = 0.01 autoRudderK = 16.0*2.0 autoRudderWyK = 8.5*3.0 autoRudderWyLowTauInv = 0.5 autoRudderDampK = 0 autoRudderOutTauInv = 1.2 takeoffHelperK = 100.0 takeoffHelperWyTauInv = 0.7 propBodyShakeK = 60.0 propBodyShakeHor = 1.0 propBodyShakeVer = 0.2 propBodyShakeLim = 900.0 detonationShakeK = 0.223 automationFlags = 0
  15. Once you are rolling at a reasonable rate (almost immediately), make sure you relax the back pressure on the stick to allow the tail to rise, (I tend to give a little fwd pressure at first), at the same time, keeping a careful eye on the left/right slippage (compensate and cancel as described with firm rudder inputs). If you think the Spit is tricky, have you tried the FW-190? Personally, I'm not convinced that the springing and drag of the gear is right. Certainly, most of the config that sets these things up seems to be cut n pasted from other aircraft. The amount the tailwheel can bounce was like having a strut made out of power-balls. I haven't checked it lately so I'm not sure it is still like that.
  16. Still there in latest update (1.5.7.10175). Although it is now fixed in the Alpha, so I remain hopeful.
  17. It's fixed in the Alpha, but not the release. Why? who knows. Now back again in 2.5.
  18. Don't USN Pilots wear flying gloves? Tut! Some of the glare in the video is in-camera, something that DCS for some reason seems to want to simulate, that and lens flares. I don't know about you guys, but my eyes don't get lens flares.
  19. From what I can see, the Radar cursor command is just a simple Key Down makes it move, Key UP makes it stop moving affair, and your hat is repeating that keystroke in the same way that a keyboard does it. (check mods\aircraft\flaming cliffs\input\f-15c folder for default.lua) If this were a WH or a Saitek stick, it would be a simple matter to use the stick scripting / profile programming SW to alter the repeat speed of a control. Is there a way you can do this for your MS stick?
  20. Multi monitor label Bug is still present in latest update. 1.5.7.8899
  21. Load the Quickstart mission, The aircraft is almost ready to go - apart from trim settings. Just don't bother with the NTR Quickstart Takeoff mission if you have 2.0 It is near impossible IMO. The runway isn't much wider than the Spit. The Quickstart Takeoff mission on 1.5 is much easier to cope with.
  22. The mechanics in the sim that must not be named are fairly recent, and came in only with v4.33 in late 2015 I believe. They are good though, it certainly reminds you that you need to monitor your loadout and cruise configurations if you don't want to spend half the mission bobbing about like a numpty. And you could argue, given it's lineage, that DCS is just as old... changed beyond recognition, true, but just the latest in the line. Their main advantage is that they have access to all the code...
  23. But the pixel resolution and frame rate of our eyes, brain & the real world are much higher than a PC screen, therefore simulations compensate for this with tricks like enlargement or black dots. Also, specularity and flashes from movement & reflected light are easy to spot in RL compared to the simulation, even in our peripheral vision.
  24. So if you don't use SweetFX and just manually set your Monitor config to use the same percentage less for your 3d screen using x= and Width= to define the edges, what difference will there be? Isn't is going to be very similar? BTW If you did it that way, it would also not affect your GUI settings.
  25. You are looking in the wrong part of the forum. This is related to performance. Check this (just one of the threads related to this problem):- https://forums.eagle.ru/showthread.php?t=190510
×
×
  • Create New...