

lmp
Members-
Posts
1285 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by lmp
-
Looking for HOTAS Setup Ideas for Su-25 Frogfoot
lmp replied to SnowTiger's topic in Su-25 for DCS World
Su-25 is not a Belsimtek product. The "vanilla" Su-25 (the payware one) is a part of the Flaming Cliffs package and has a subforum here: http://forums.eagle.ru/forumdisplay.php?f=281 For the Su-25T I guess the main DCS World subforum would be the best place? http://forums.eagle.ru/forumdisplay.php?f=184 Cheers, -
That's an Mi-6, the predecessor of the Mi-26 that we have in game. In its time it was the biggest and also the fastest helicopter in the world.
-
Where did you get the idea that the MiG-15 had no ejection seat or air conditioning?
-
The limits in the manual don't tell you what's the maximum weight that you can land and still walk away from it. They're this low because they're designed to limit wear and tear and guarantee (with a hefty margin) a safe landing regardless of whether the airplane your flying is brand new or 20 years old. That said, if you don't care that much for sticking to RL procedures, you should have no problem landing the aircraft with well over 1000 liters and externals stores. I usually try to get the fuel below 1000, so I can land with a bit more grace. After all, burning fuel in the MiG is NOT a problem. Do one extra circuit in afterburner and you've lost plenty :).
-
Su-25 Frogfoot in FC3 - Cold War Warrior Campaign with Tacview
lmp replied to Bunyap's topic in Su-25 for DCS World
Ah, this campaign is so much fun. I just got through mission four. I got to my station safely despite being tracked by the Phantoms a couple of times and started circling. After a few minutes I got told to turn north and engage an MLRS battery. That got me right in the middle of a dogfight between three Phantoms and a couple of MiG-23s. I got behind one of the Phantoms and hit him with two R-60s but then a Flogger swooped in and stole my kill. Game calls it his, I call it shared :P. In the meantime another Phantom got behind me and fired a few round into me before being taken care of by number two and another Flogger. At this point I had no gunsight and trouble flying straight, but nonetheless I did a few circles and found the battery. I fired my eight S-25s and scored four hits, but no kills. Then I diverted to Maykop and after accidentally flying right over a Roland which, fortunately, was out of ammo, I landed on fumes. Debriefing gave me 0 air and ground kills and a score of 75, but I still had plenty of fun ;). -
Consider what weapons you have left and how much fuel is there in the tanks. There is a section in the manual discussing it.
-
Su-25 Frogfoot in FC3 - Cold War Warrior Campaign with Tacview
lmp replied to Bunyap's topic in Su-25 for DCS World
The S-25 is the younger, bigger brother of the S-24. It's twice as heavy, has better ballistic performance and a bigger warhead. Inspired by Bunyap I did the first two missions of the campaign today and yesterday and I took a load of four S-25s on both. I fired all my missiles in a single run. I managed to kill 2 Leopards in the first mission and 5 or 6 artillery pieces in the second. The rockets are a joy to use :). -
Su-25 Frogfoot in FC3 - Cold War Warrior Campaign with Tacview
lmp replied to Bunyap's topic in Su-25 for DCS World
S-24 rockets are not laser guided. S-25 rockets have a laser guided variant (S-25L). All three (S-24, S-25, S-25L) work well against armor, are generally easy to use and accurate. It's my weapon of choice for the Su-25. -
Hey, you could have pledged the missing $40k+ if you thought the project looked so great ;). I decided it's not something I need in my life, so I didn't support the kickstarter - I don't see how that makes me a worshiper of anything ;).
-
Sure, I'd buy it over some teen fighter.
-
Leatherneck Simulations Monthly Update - January 2015
lmp replied to Cobra847's topic in Heatblur Simulations
Is a Saab harder to research than a MiG or a Tomcat? I have no idea frankly. -
Leatherneck Simulations Monthly Update - January 2015
lmp replied to Cobra847's topic in Heatblur Simulations
Here's an idea for you. Since Cobra is from Sweden, maybe the "duck" is a Viggen? Wikipedia says the name means: "Thunderbolt", ambiguous with "Tufted duck". http://en.wikipedia.org/wiki/Saab_37_Viggen -
You need a stick and throttle, they said...
lmp replied to siraccord's topic in Screenshots and Videos
I'm glad you're having fun and I agree with you. I don't like that so many people on this forum are trying to convince newcomers that you need gear worth a few hundred bucks in order to enjoy the game "properly". I'm sure most of us here got into flight sims with just a cheap, plastic joystick (or none at all - like you). Getting to the point where you're ready to shell out a small fortune for a Warthog or TrackIR is a process. I guess some people forget they went through it. You don't start a new hobby by buying the best possible gear. -
Thanks again PilotMi8 :). The MiG is looking great so far, I can't wait to fly it :).
-
The OSP-48 comprises of: ARK-5 automatic direction finder, MRP-48P marker beacon receiver and RV-2 radio altimeter, right? Nothing fancier than that?
-
So a mix of the old and the new? Thanks! :)
-
It doesn't look cartoony to me. Also, I think it's one of the best looking cockpits in the game.
-
The description never mentions which guns we're getting (NS-23, NS-37 versus NR-23, N-37). Is it also something that's being discussed? :)
-
In the MiG-21 and the Su-25(T) there's plenty of stuff obscuring your view (canopy frame, mirror in the MiG, gun camera). Being able to look around them is a lifesaver in combat. After a little practice I got used to 6DOF and in the long run it's probably better idea than turning it off.
-
There's the ARK-UD which is a type of emergency beacon locator but AFAIK the presets aren't typically (or at all) changed. The set of emergency frequencies programmed is standard - I found the same frequencies we have in the game in a description of the ARK-UD unit from an Antonov transport plane. That's why I didn't mod that in as well. Oh, and I missed one question from Cibit - no, I don't believe this fixes the "nav mode" of the R-828, but I haven't tried it, so maybe by some miracle it does ;).
-
I didn't specify the modulation for the R-863 in the panelRadio object, I think it'll depend on how the FM/AM switch is set. TBH I haven't tested it in FM mode, but that's how it worked when I edited the frequencies manually in the R-863.lua earlier - the radio respected the FM/AM switch whether I was using the dialer or stored channels. The R-828 only works in FM, so I put that modulation in the panelRadio object.
-
I figured a description how to do it yourself may remain relevant longer in case there are some minor changes to these files in future versions. Also, this way you can easily apply a similar solution to the R-828 in the Ka-50. I'm glad it worked for you, Cibit :).
-
I can always talk with my ground crew, regardless of the switch position. Are you sure you were on a friendly airfield? ;)
-
It should be easy to do for the Ka-50 as well, though I haven't tried it. First, disclaimer: I take no responsibility for whatever damage this may cause. It worked for me with the current version of the game, it may not work for you or with a different version. Always back up the files you change. Right, so first I added a panelRadio object to the Mi-8MT.lua file, which describes the structure of the form in the radio tab of the editor. The Mi-8MT.lua file lives in the Scripts\Database\helicopters directory inside your DCS World folder. Similar Ka-50.lua file is also there, but files for other aircraft are sometimes in different places, like CoreMods\aircraft\<aircraft name>. I don't know the reason for this. My panelRadio object looks like this: panelRadio = { [1] = { name = _("R-863"), range = {min = 100.0, max = 149.0}, channels = { [1] = { name = _("Channel 1"), default = 120}, [2] = { name = _("Channel 2"), default = 121}, [3] = { name = _("Channel 3"), default = 122}, [4] = { name = _("Channel 4"), default = 123}, [5] = { name = _("Channel 5"), default = 124}, [6] = { name = _("Channel 6"), default = 125}, [7] = { name = _("Channel 7"), default = 126}, [8] = { name = _("Channel 8"), default = 127}, [9] = { name = _("Channel 9"), default = 128}, [10] = { name = _("Channel 10"), default = 129}, [11] = { name = _("Channel 11"), default = 130}, [12] = { name = _("Channel 12"), default = 131}, [13] = { name = _("Channel 13"), default = 132}, [14] = { name = _("Channel 14"), default = 133}, [15] = { name = _("Channel 15"), default = 134}, [16] = { name = _("Channel 16"), default = 135}, [17] = { name = _("Channel 17"), default = 136}, [18] = { name = _("Channel 18"), default = 137}, [19] = { name = _("Channel 19"), default = 138}, [20] = { name = _("Channel 20"), default = 139}, } }, [2] = { name = _("R-828"), range = {min = 20.0, max = 60.0}, channels = { [1] = { name = _("Channel 1"), default = 20.0, modulation = _("FM")}, [2] = { name = _("Channel 2"), default = 21.0, modulation = _("FM")}, [3] = { name = _("Channel 3"), default = 22.0, modulation = _("FM")}, [4] = { name = _("Channel 4"), default = 23.0, modulation = _("FM")}, [5] = { name = _("Channel 5"), default = 24.0, modulation = _("FM")}, [6] = { name = _("Channel 6"), default = 25.0, modulation = _("FM")}, [7] = { name = _("Channel 7"), default = 26.0, modulation = _("FM")}, [8] = { name = _("Channel 8"), default = 27.0, modulation = _("FM")}, [9] = { name = _("Channel 9"), default = 28.0, modulation = _("FM")}, [10] = { name = _("Channel 10"), default = 29.0, modulation = _("FM")}, } }, }, I added it to the third argument of the function returned by this script, or more specifically, right after this block of code: HumanRadio = { frequency = 127.5, minFrequency = 100, maxFrequency = 400, modulation = MODULATION_FM }, This should make the radio tab appear for playable Mi-8s in the game... only it won't, because the radio tab can only be enabled for airplanes. Fortunately we can change that easily in another lua file: MissionEditor\modules\me_aircraft.lua. We will be changing function verifyTabs(). Lines 1244 - 1290 should contain this: if (__view__ == 'helicopter') then if (unitTypeDesc.Navpoint_Panel == true) then _tabs:showTab('navPoint') else _tabs:hideTab('navPoint') end if (unitTypeDesc.Fixpoint_Panel == true) then _tabs:showTab('fixPoint') else _tabs:hideTab('fixPoint') end _tabs:hideTab('waypoints') else if ((unitTypeDesc.Waypoint_Panel ~= nil) and (unitTypeDesc.Waypoint_Panel ~= false)) then _tabs:showTab('waypoints') else _tabs:hideTab('waypoints') if _tabs:getSelectedTab() == 'waypoints' then _tabs:selectTab('route') end end _tabs:hideTab('navPoint') _tabs:hideTab('fixPoint') if (unitTypeDesc.panelRadio ~= nil) then _tabs:showTab('Radio') panel_radio.update() -- ńčíőđîíčçčđóĺě ÷ŕńňîňó local frequency = tonumber(e_frequency:getText()) if not frequency then setDefaultRadio(true) frequency = tonumber(e_frequency:getText()) end panel_radio.update() panel_radio.setConnectFrequency(frequency) else if _tabs:getSelectedTab() == 'Radio' then _tabs:selectTab('route') end end [b][color=DarkRed]end[/color][/b] We want to move the last "end" (the one I marked) in this block to line 1271, right before if (unitTypeDesc.panelRadio ~= nil) then Once we do that, the radio tab and the form in it should be visible in the ME. Now we need to make them work. I have no idea how aircraft like Sabre or Fw-190 read their radio settings from the editor, so I did it the way LNS did it in the MiG-21bis. I'm not sure it's the cleanest way, but it works. Go to Mods\aircraft\Mi-8MTV2\Cockpit\Scripts\Devices_specs\Radio and edit the R-863.lua file: dofile(LockOn_Options.common_script_path..'Radio.lua') dofile(LockOn_Options.script_path.."mission_prepare.lua") local gettext = require("i_18n") _ = gettext.translate frequency_dial = {limit = {100E6,399999E3}, dials = {{157,100.0,1E7, shift= 10, limit = {10,40}},{158,10.0,1E6},{159,10.0,1E5},{160,100.0,1E3,limit = {0,100}}}} innerNoise = getInnerNoise(2.5E-6, 6) frequency_accuracy = 1000.0 --Hz band_width = 25E3 --Hz power_MW = 10.0 -- Power in metric range, Watts power_DMW = 8.0 -- Power in decimetric range, Watts agr = { input_signal_deviation = 50.0, --Db output_signal_deviation = 5.0, --Db input_signal_linear_zone = 10.0, --Db regulation_time = 0.25, --sec } [color=DarkGreen][b]presets = {} if get_aircraft_mission_data ~= nil then local radio_from_mission = get_aircraft_mission_data("Radio") local radio_1 = radio_from_mission[1] if radio_1 then for i = 1,20 do presets[i] = (radio_1.channels[i] or 131 ) * 1e6 end end end[/b][/color] GUI = { ranges = { {min = 100E6, max = 149975E3, step = 25E3}, --Hz {min = 220E6, max = 399975E3, step = 25E3} }, displayName = _('R-863'), AM = true, FM = true, [color=DarkGreen][b]channels = presets,[/b][/color] } And R-828.lua: dofile(LockOn_Options.common_script_path..'Radio.lua') dofile(LockOn_Options.script_path.."mission_prepare.lua") local gettext = require("i_18n") _ = gettext.translate innerNoise = getInnerNoise(2.5E-6, 6) frequency_accuracy = 1000.0 --Hz band_width = 25000.0 --Hz (6 dB selectivity) power = 10.0 --Watts agr = { input_signal_deviation = 50.0, --Db output_signal_deviation = 5.0, --Db input_signal_linear_zone = 10.0, --Db regulation_time = 0.25, --sec } presets = {} presets[1] = 21500000.0 -- frequency in Hz presets[2] = 25675000.0 -- radio Mayak presets[3] = 27000000.0 presets[4] = 28000000.0 presets[5] = 30000000.0 presets[6] = 32000000.0 presets[7] = 40000000.0 presets[8] = 50000000.0 presets[9] = 55525000.0 presets[10] = 59975000.0 [color=DarkGreen][b]if get_aircraft_mission_data ~= nil then local radio_from_mission = get_aircraft_mission_data("Radio") local radio_2 = radio_from_mission[2] if radio_2 then for i = 1,10 do presets[i] = (radio_2.channels[i] or 20 ) * 1e6 end end end[/b][/color] ElecConsumerParamsLight = {0.5, true} GUI = { displayName = _('R-828'), AM = false, FM = true, } GUI.channels = presets --settings squelch = true volume = 0.5 channel = 0 max_search_time = 5.0 TRANSIVER_FAILURE = 0 ANTENNA_FAILURE = 1 Damage = { {Failure = TRANSIVER_FAILURE, Element = 4, Integrity_Treshold = 0.3}, {Failure = ANTENNA_FAILURE, Element = 58}} Adding the bold, green parts. That's all :).