Jump to content

Raistlen007

Members
  • Posts

    105
  • Joined

  • Last visited

  • Days Won

    2

About Raistlen007

  • Birthday 08/19/1985
  1. Placebo. Just tested. Wing still drops it like it's hot.
  2. I as well would like to know what the developers feel about this issue. The stall behavior definitely impairs enjoyment of the module to some extent. Even an acknowledgement that they won't be looking into it because of internal priorities is a valid and honest response.
  3. There's an error message of your SPI is too high or higher than your current altitude. This can also happen if your target altitude is set manually and not automatically (DTS.) The generic error for being unable to compute a drop is CCIP INVALID.
  4. Make sure you put in the leading zero. You can't input just 38 degrees east, it needs to be 038, Zero three Eight at the start
  5. Hover with the mouse over the grayed out square, note the little black triangle on the top right, click it, then select 'buttons'
  6. TGP Being SOI is not a requirement. the TGP needs to be pointing at some point on the ground. Got a track?
  7. In DCS you have to input the wind data into the CDU manually. In real life it automatically updates.
  8. Same here. For some reason Windows 10 has issues with my phone and diskonkey USB drivers. It keeps showing up as 'unknown device' and I keep having to reinstall the drivers, and when I do, the MIG21 needs another activation. And best part is... the activation often fails for some reason and then I have to erase it from the Registry and do it again. I'm down to 4. This is the only module that gives me issues. Please please please fix this!
  9. Sounds pretty good, but honestly I can't really tell the normal and reversed apart, but I think it's soft enough.
  10. The end transmission sound I think would get a little jarring after a while. Maybe it could be softened it up a tad?
  11. Some quality of life improvements made in the real A-10C would be nice, but I don't know if they exist in the currently modeled suite, such as deleting markpoints, make last markpoint SPI, and maverick toggle ground stabilize, but I agree that have pretty much moved on and these additions will likely never be implemented.
  12. Can you please clarify what we could submit that would be helpful? If we can't link to any USAF document because they're "classified" and ED can see them anyway... and HUD video is dismissed because "you can't recreate the exact conditions" and A-10 pilot input is dismissed because "muscle memory is not a substitute to data" and expertise of ground crew is dismissed because "not hard data"... I would seriously, no sarcasm, like to know what would be helpful here? Because right now I feel like this is an artificially constructed catch-22.
  13. The file is \Mods\aircraft\A-10C\Cockpit\Scripts\IFFCC\IFFCC_param.lua The relevant section is: function ReadHUDOptions(f) local str str=f:read() local temp str, temp = GetStringField(str) str, temp = GetStringField(str) local SPEED_OPTIONS_STRINGS = {} SPEED_OPTIONS_STRINGS[0] = "Indicated" SPEED_OPTIONS_STRINGS[1] = "True" SPEED_OPTIONS_STRINGS[2] = "Ground" -- AIRSPEED_DISPLAY_OPTIONS -- SPEED_OPT_IAS, -- SPEED_OPT_TAS, -- SPEED_OPT_GS, -- SPEED_OPT_MACH_IAS GetValueFromString(IFFCC_data, "SpeedDisplayOptions", TrimStringLeft(TrimStringRight(temp)), SPEED_OPTIONS_STRINGS) --TO DO: ЗАПОЛНИТЬ ТАБЛИЦУ РЕАЛЬНЫХ ЗНАЧЕНИЙ str, temp = GetStringField(str) str, temp = GetStringField(str) if nil ~= string.find(temp, "Numerics", 1, true) then IFFCC_data["Tapes"] = false else IFFCC_data["Tapes"] = true end str, temp = GetStringField(str) str, temp = GetStringField(str) if nil ~= string.find(temp, "Standard", 1, true) then IFFCC_data["Metric"] = false else IFFCC_data["Metric"] = true end end Changing what you want from true to false is the easy bit. I'm sorry but I don't know the rest. It's something I know others have figured out, but the relevant post links to a database that's no longer there.
  14. I can understand wanting to have the settings already there so you don't have to adjust them. You can change them in the .LUA to be permanent settings. I don't recommend using flight -> prepare. In my experience it breaks more than it helps.
  15. The built in loadout window will give you your weight but not rotation speed.
×
×
  • Create New...