Jump to content

Migow

Members
  • Posts

    355
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. hello ED team i would like to know the map parameter for UTM projection lon0 central meridian of the projection (degrees) is 147°(correct me ) i think but i need the correct "a (equatorial radius)" and either "f (flattening of ellipsoid ) "or "b " . also"k0( central scale factor) "( i guess 0.9996) thanks by advance my regards
  2. hi , i found a good Fix for the periscope issue , problem solved find the file in {DCS World directory }\Mods\aircraft\Mi-24P\Cockpit\Scripts\9K113_CAM\9K113_CAM_init.lua then at line 18 swap local x,y,w,h,GUI_scale = get_UIMainView() by local x,y,w,h,GUI_scale = 0,0,3840,2160,2--get_UIMainView() resolution is 3840 / 2160 scale 2 for me , set your parameter it will work!(remember it is x,y,w,h,GUI_scale) (dont forget to put comment with get_UIMainView() -- or get rid of it whole file corrected. dofile(LockOn_Options.common_script_path.."devices_defs.lua") dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") local use_helmet = false use_helmet = LockOn_Options.screen.oculus_rift purposes = {render_purpose.AUXILLARY_SIGHT_SCREENSPACE} if use_helmet then indicator_type = indicator_types.COLLIMATOR purposes = {render_purpose.AUXILLARY_SIGHT} else indicator_type = indicator_types.COMMON purposes = {render_purpose.AUXILLARY_SIGHT_SCREENSPACE} local x,y,w,h,GUI_scale = 0,0,3840,2160,2--get_UIMainView() dedicated_viewport = {x,y,w,h} dedicated_viewport_arcade = dedicated_viewport end page_subsets = {LockOn_Options.script_path.."9K113_CAM\\9K113_CAM_base_page.lua"} ---------------------- pages = {{1}} init_pageID = 1 the issue come from get_UIMainView() it report incorrect parameter!
  3. thanks for your investigation :thumbup: ok , first i 'm not native english , so it likely hard for people to understand what i'm trying to explain ,the way etc...^^ 330 km/h IAS in forward flight with 0 m/s VVI at 50m msl ,in your example you are diving a little at 4m/s not the same thing i said 330 km/h to show you that the animation is sync with flight model , there is no bug in animation ( at least in forward flight) the subject is mostly about rotor clearance , check the rotor clearance it must match the data "Your still talking about this clearance of blades at speed, most of what you are taking about is theoretical" not correct the data come from real flight test in all kind of maneuver even forward flight please check the rotor clearance in your video ,fly at same parameter than kamov data full forward flight 0m/s VVI the thread is about that ; if possible slow down the video look at rotor at 47° 107° like in document 90% time in your video must look at rotor clearance 47° 107° you talk about flight enveloppe , i talk about rotor clearance , we dont talk about the same problem :) i'l make video about that like you say it is very unlikely that flight model will change . still people and ED need to see that something is wrong with rotor clearance, and by the way flight model likely the deviation is about rotor Dissymmetry of lift
  4. i hope we have an upgrade bs3 , either crowfunding or something , i just want thing done right :)
  5. this is bug report ,i don't understand why people said go buy hind , or don't report bug in this thread .... :doh:, truth need to be told:) let stick to bug report plz thx thinkr ,26-J39 for support let makes blackshark great again :D to David OC maximum combat load is 10800kg , beyond that it is ferry load , maxium g is 1.5 in game you can take 3g without airframe stress or catastrophic failure , another flaw but less serious. the rotor break at 330 km/h , the animation match the flight model, the flight model don't match the real thing , if what you told was correct then nothing would happen( animation desync)? in real life forward speed at 320km/h give 750mm clearance , still more than 1/2 clearance 100mm difference between 300 km/h 320 km/h . in game ,about to collide. remember 500mm safety from kamov , and we have 750mm here i 'm not rude , you are the one rude toward me ,i post real fact you claim i post lie now?my document are from kamov , the best source for this helicopter you can find , i just told the truth still thx for investigating :) how can you say that " for what he believed to be a major fault with the Ka-50 and showed no real evidence " test again the animation match the flight model in the past real pilot questionned the low rpm condition as not realistic , idle engine too powerful , autorotation unrealistic ,ed was evasive :sad
  6. this is not simulation when you have 850% deviation , on clearance there are completly off , i can't believe it. to get this kind of deviation ,mathematical is seriously wrong, when you have small deviation you can fix with hack , but here? the data are based on real flight not only theoretical calculations . airframe is from 89 it is the same the standard production. game should nearly match in standard condition... helicopter is in normal combat loadout 9800kg mass in test , not empty ... in maximum combat loadout it is 10800kg mass. the issue it still the same i wish i had found those document in 2009... likely nothing will change...
  7. it is hard to get both rotor at good position on screenshot ,better a video do it by yourself you will see with good point of view how close they are in game :thumbup:
  8. hi it feels weird but i found docs about ka50 Aerobatic Flight :cold: five docs to read ERF1998-vol1-AD05.pdf 64.pdf burtsev_soosniy_nesuschiy_vint.pdf ERF1998-vol1-AD04.pdf ERF-1999-G22.pdf simple , the simulated ka50 doesn't not match the real one:( in all version of game since BS 1 /2 , DCSworld 1/2/2.1 (it was even worse in BS1 ) in forward flight 9800kg 20°C 50 meter msl 760mmhg irl first at 300 tas km/h rotor minimal clearance is 850mm irl almost 2/3 clearance , in game at 280km/h it looks like less than 100mm , about to collide irl : at 0 km/h clearance is 1400mm at 300km/h clearance 850mm 700mm at 320km/h dive can be done at 390 km/h rotor blade tip reach 1.0 mach in game also 90/80° flat turn at 220 km/h seems impossible (can be done at 180 km/h) check clearancies at 45° , 107° kamov consider more than 500mm clearance safe , all maneuvries at worst go close to 500 mm clearance , the real one is far safer at high speed , more agile, this is very serious deviation , we dont talk about 10% deviation:( , we have 850% deviation just in forward speed ,irl when we include maneuvries we still get minimal 500 mm clearance at 300 km/h in game you crash this why we broke the rotor so easy , when it should not , and why the alarm is useless in game, IRL it is very safe at high speed , we are flying a complete crippled different machine :( kamov use ULISS6 (ULYSS6?) mathematic model , in worst case they have less than 100mm clearance deviation they underestimate the clearance, irl it is safer^^ i guess ED don't use uliss6 the deviation are massive between uliss6 and ed :( summary , the flight model is seriously flawed , irl and game is like complete different beast:doh: in game we have a crippled helicopter , unsafe as hell that can't go fast and maneuver safely need official answer about that :3
  9. Autopilot Replacement i'm working on app to replace dcs faulty autopilot :doh: the app get input then talk to the game so summary : currently in the game the autopilot fight pilot hand on which should never happen ,irl there is no problem the autopilot add massive error on attitude after trim , irl there is no problem hover with 1 % autority .... in my app: the app simulate the rudder micro switch with axis: push the micro switch(the brake axis) (without the need to move the rudder axis) then the autopilot dont fight pilot like mi8 , it work very well :thumbup:, it has to be like this irl there is no other way for yaw autopilot? for cyclic :when you move the autopilot don't fight the pilot (i tried to simulate the compensator to prevent fighting the autopilot) , the problem is when you move back at the center , the autopilot try to keep attitude in attitude mode so there is still some movement no so smooth unlike the real thing when you pass the center so i'm questionning in the real thing did they implement a handon , handoff microswitch on the cyclic?:huh: auto turn can't work , how can i get shkval's azimuth in export? hover is buggy WIP:cry: so i ask AlphaOneSix , or airtito ;) how handoff handon cyclic autopilot is working in kamov helicoper, compensator seems not enough, the real thing always move seamless
  10. ok then no bug ? then where are the chart?:) it 'll try to make chart. thx for answer:)
  11. autopilot authority hi alphaonesix : what is the 20 % autopilot authority ? EX: if i have a cyclic than have a Y (pitch)range [+100 ; -100 ] the cyclic is trim to +20(cyclic range) to get -10(whatever doesn't matter) pitch attitude(not cyclic range) , the autopilot can move is own Y range [+20 ; - 20]. To keep attitude the total sum : pilot( cyclic in rest) + autopilot could move up to [+40; 0]?:)
  12. vikhr ratio was good in BS1 , IRL it's 85% - 95% hit. starting with DCS WORLD it go low :( , i'll provide video if it's crosswind it's another story:)
  13. mig21 is dangerous to fly , too much accident ,they add useful AOA alarm especially in combat to avoid stall. well training irl will not tell you how to avoid ka50 dangerous flight envelope , if you enter you die, it is like black hole event horizon :D of course in game you can train about dangerous flight envelope :thumbup: coaxial detractor might be right in the end, it is too dangerous to operate with such flaw :( yoyo told me there is no chart about rotor collision hazard :( at high altitude 3000 m 20°C at sea level 760 QNH dangerous flight envelope start 150 km/h it make the helo very slow to keep agility :( rotor collision hazard require 4 variable charts which depend on speed , altitude , temperature, pressure. many charts , and in dynamic meteo even worse :(
×
×
  • Create New...