Xxx

Excellent! Have some rep! Best Regards David

Dear fellow Beacon hunters. I have managed to get a couple of RSBN beacons working, but the rest remain stubbornly off! It seems that after aTACAN entry, I can not add a RSBN entry. Here is where I am stuck;- My programming skills are none existant. So I think I will wait for one of you wiz kids to finish the job. airdrome = { TACAN(31, 'X', 'TSK', {x = -281653.7, z = 647182.6}) } }, { type = BEACON_TYPE_RSBN, callsign = "SI", frequency = 831000000.0,-- channel 31 channel = 31, position = coordinates("42'14'25N 042'02'48E"), }, Looks a mess doesn't it? Hope you guys get the map done, then we can share some rep's! Regards David

You sir, are a Steely eyed missile man! Rep inbound! Your mod is perfect! ED should ask you to do ALL the runways in the NTTR and ALL the runways in the 1.5 Caucuses map! And slip you some cash as well! Then we can fly the L39 everywhere with full navigation! Thank you for this mod. Best regards David

Thanks Max. I will give it a test flight tomorrow. Cheers.:)

A Tonka would be great. However how would the navigator, or weapons electronics officer be implemented? With two seat attack aircraft, unless you have a shared cockpit, the pilot would have to do both jobs? The Viggen is the Swedish answer to the Tornado. Accomplished with a crew of one and modelled to a high degree of perfection, by LN, if I may say so. :thumbup: In the Tornado, I just worry about that missing guy in the back. Unless he can be automated of course. I have thought many times if the Just Flight Tornado could be ported over to DCS World, it will be epic!:D Cheers David

Hi Max. The attachment link in your post goes to an invalid attachment link? Is there another one? Flying around the Nevada map in the L39 without navigation beacons is just very unrealistic!:music_whistling: Regards David

Yes, thanks for the information. I think the RSBN/PRMG seems a bit of a mess then? The Mig 21 and L39 using RSBN/PRMG but different code in different sims. The whole RSBN/PRMG needs to be standardised as one code. Then those mobile transmitters could be used in all the maps. For now it looks like the MIG 21 can navigate in NTTR map, using its in built coded RSBN/PRMG receiver that's specific to the LN Mig 21 and not the actual map. The L39 can tune the NDB frequencies with its variable tuner but NDB is inadequate for combat navigation. Even if there were NDB's in Nevada, its still far from ideal to navigate over a desert range! Still a shame the 1.5 map has only 4 RSBN stations that the L39 can use. This means the map to the south can not be navigated! A real shame, since this L39 sim is one of the best simulation aircraft models I have seen, anywhere! Including FSX/P3d. Hope it gets sorted out in the future? Please! Best Regards David

The portable RSBN is an important idea for ED to consider. Its realistic and fits with the "historic" nature of the aircraft flown in the 1.5 map. Apart from the Ka-50 (GPS) and SU25, we are in need if some radio beacons to find our way to targets, if flying those jets. The post prior to this has a guy doing a mod for RSBN use in the 2.0 Map. This is great news for the L39/Mig21 drivers, but in that area, just purely academic, since there will never be a conflict using older Russian jets in the Nevada desert. However it would at least permit pilots of the L39/Mig 21 to navigate the area. Also aid the creation of Red Flag type scenarios using the L39 and Mig21. My original post has stimulated this great idea of the mobile, front line RSBN units. I enjoy creating scenarios in the mission editor and would welcome the addition of the mobile RSBN. I hope it gets added. Or at least a way to use the Mig 21 RSBN receiver in the L39? The primary aim being to navigate accurately around the whole 1.5 map! Once we can do that, accurate ground attack missions, in poor visibility, may be flown. The mission designers can then prioritize RSBN units as game changing targets. Just as the TACAN/Vortex/NDB /Satellite transmitters would be priority for any enemy. Looking at the Viggen, that is possibly the only aircraft that can operate fully autonomously in a hostile zone. Not needing any help from transmitters to find the target! Way to go Saab!:thumbup: Cheers:)

A mission to remove an armoured column, holding a bridge, in a steep sided valley. Defended by A SA13 and the weather, fog, low cloud, low viz.:smilewink: Cheers David

Yes! Now that would e a fine addition to the Mission Editor.:thumbup: I am not just trying to enjoy flying over the entire 1.5 map, but create some missions. Being somewhat spoiled by the navigation in the Viggen (automatic computerised dead reckoning), the Hog (GPS) and the Ka-50 (GPS). With a mobile RSBN station, we could navigate anywhere in DCS World 1.5, or 2.0(when the current release bug is sorted).......hey, even the Normandy Map?:smilewink: Can ED code these please and add them to the Mission Editor!:thumbup: Regards David

Thanks, lets hope the guys at ED can "enable" those old transmitters. I have the tuning numbers for the pre 1.5 map, sadly they don't work. This is little beauty of an aircraft, shame its limited to ADF only:cry: Best regards David Edit. I just read that the L39 is bugged after the latest 2.5 update, but to be honest I have not yet tried it in 2. Surely you can't navigate this aircraft in North America? No VOR/ILS/TACAN...?

Having just bought the L39 I am disappointed to see that there are only 4 air bases that use the RSBN navigation and landing system. :cry: The old RSBN stations are "realistically" out of action! Since this is a Russian navigation system. This leaves only the ADF for navigation. All the station codes must be there somewhere. Pre DCS 1.5 they were implemented? Is there a mod or any way I can tune to the old RSBN stations, I the south. With such a superb simulation, its spoiled by the lack of navigation points. Thanks

So what would your airspeed indicator show, given a 100 knot headwind, in order for you aircraft to stall? Indicated Airspeed is the speed of the wind entering the Pitot tube and thus the airflow over your wings. Your ground speed would indeed be 0, but your airspeed, referencing your airspeed indicator, would be 100 knots. Or if you went below stall speed, 99 knots. I will have to get to differ with your statement that wind speed has nothing to do with stall speed. Airbus build a safeguard into their landing speed, called Mini GS. The computers detect wind speed (head wind, crosswinds or tail wind and factor the wind speed into the final approach speed. The reason is to avoid approaching stall speed. Thus, Airbus believes wind speed components have an important affect stall speed. Just my opinion sir, not everyone can agree in this world.:-) On the subject of the Viggen. At moderate speeds 5 m/s headwind, I couldn't tell much difference on take off or landing. The flight path indicator was doing a fan dance as the aircraft settled on course. Could be the Doppler adjusting the course calculations. My wing man crashed on landing, but that's nothing to go by..:doh: Regards David

I don't follow that. Just for example, If your stall speed is 100 knots IAS and you are flying directly into a headwind of 20 knots, then surely your IAS stall speed is 80 knots IAS? Similarly, if you have a tailwind of 20 knots, your stall speed will be 120 knots. At least that's my understanding. However, in this topic, if the airspeed is not reported as such on our ASI, then there's a problem. :cry: Off topic the L39 has a dual readout, IAS and ground speed....very handy! But not in our Viggen! regards, David

Thanks for that! Great news! :) I was putting together a mission to attack an escorted convoy, but without wingmen and additional weapons, the convoy escorts always win! Thanks again for this simulation, havn't enjoyed one as much for years!:thumbup: Regards David

Copy that. The HUD is set to low position, its my speed that's a bit slow....That's what you get by flying around in the Hog for years!:music_whistling: Tell you what though, its easier to put a GBU on the spot from 10k, in the Hog, that prosecute a high speed CCIP, low level run against a defended armoured column!:smilewink: Cheers David

Not wanting to post this as a criticism, since this simulation is a real beauty....:thumbup: I have noticed AI wingmen don't carry the Rb15F, after arming them in the mission planner. When tasked to attack ships, they oblige, but fire an invisible short range missile? (OK against unarmed ships but suicidal against warships) I use the special Rb15F for AI in the mission planner, but no joy. Also the code 800001 is the only one that seems to work.(I think this is a work in progress) Regards David

:lol: That Fart Kontrol is priceless! I must learn Swedish! Copy the LN manual. I have more or less got the CCIP release, however I seem to still require a slight dive to see the Piper and Circle. This is probably going to be my attack mode of choice. The others always drop a bit long. Still its a work in progress..my weps learning that is!:book: The LN manual also doesn't have a min range for the Rb15F. I have failures inside 30 Nm...But again its probably me? Regards David

Exactly! As you say, these are guides!:book: The LN manual states its in "beta". A great many illustrations are missing/not implemented. The CCIP method is given as; "CCIP The CCIP (Continuously Calculated Impact Point) mode is used when the bombs are fitted with drag chutes and in mode NAV. The reticule indicates where the first bomb in the salvo will hit if dropped “now”. The ring indicates where the last bomb in the salvo will hit. The bomb salvo will impact “between” the reticule and the ring. A target fix is not made in CCIP mode. Only barometric altitude is used for the sight calcula- tions and displayed in the HUD. The distance line does not indicate distance to the target, but whether the bomb will be released within their arming time (5.2 seconds). Selection Weapon selector: BOMB PLAN. Master mode selector: NAV. Only used with bombs with drag chutes attached (high-drag)." There are many discrepancies between Chucks guide and LN manual, in the CCIP delivery . The use of "Nav" for master mode to attack, for one. The "distance" line only appears after I arm the weapons( trigger unsafe), this gives "arming time" not distance to target, as stated in Chucks guide. The only way I can deliver CCIP high drag bombs is to adopt a pop up and dive at 30 degrees, with piper on the target, then unlock trigger, with the timeline then appearing and subsequent weapon release on the piper, given that there is sufficient arming time for the bombs, as depicted in the (arming time line) distance line. I appreciate how complex a task this must have been to program into the simulator. My hats off to the devs. When everything is out of beta things will no doubt become clearer. One things for sure, there are many hours of entertaining discoveries to be made. Cheers David

Hello. I am unable to obtain the correct HUD symbology when using High Drag bombs. I attack a target from the west, follow the procedure and do not see any 40 second countdown line. On target, the release is always long. I am using Chuck's guide thus; PREPARATION: Gather and set target parameters a) We start our attack run from Waypoint B2 and intend to attack our target, which is located on Waypoint B3. b) Read QFE of Target from Kneeboard (“RSHIFT+K” to open, “[“ and “]” to scroll pages), which is located on Waypoint B3. c) Set altimeter pressure to the QFE of the Target. d) Set Data Selector to TAKT – INPUT e) Press “9” and “B3” (desired waypoint on the target’s position) to set Navigation Waypoint B3 as a Target Point M3 f) Switch the Data Selector back to AKT POS - OUTPUT. 2. PREPARATION: Weapons Setup a) Set Weapon selector to BOMB PLAN. b) Set Impact Interval selector to 10 meters. c) Set the HUD to the LOWER position to ensure HUD data is properly displayed during bombing run. 3. EXECUTION: Perform Attack a) Set Master Mode to NAV and fly to Waypoint B2. b) Set HUD mode to “Low Altitude” by setting the SLAV SI switch to FRAN (OFF). c) Once you cross Waypoint 2 and the HUD switches from B2 to M3, reduce altitude to 100-150 m above ground level (AGL) and accelerate between Mach 0.8 and 0.9. d) Target Distance Line appears when you are 40 seconds away from target. When it shrinks down within the Target Launch Zone, set the trigger to UNSAFE by clicking on the stick’s safety cover. e) Set target between the dot (first bomb drop point) and the circle (last bomb drop point) on the HUD and drop bombs by pressing and holding the Weapon Release button until the FALLD LAST (STORES RELEASED) light illuminates. f) Evade and pull up with 5 G. g) Set the trigger to SAFE by clicking on the stick’s safety cover. h) Set Master mode to NAV. When I pass the target, without firing and turning east, I get the Target Distance Line. Its as though the system can only work from east to west? Also the system always puts the target ahead of me? I have tries disabling the Ground Moving Target "221" but no luck? If I drop on the piper, th circle is nowhere to be seen, the bombs are always long. Needless to say the Altimeter is set as per knee board, my navigation is spot on reading "5" on the Ternav. :helpsmilie: Thanks David

Exactly! However, if you use your energy efficiently, low level "dogfighting" with a slower opponent, is possible. My scenario included some helicopters, at 50 metees, loitering over the primary target. The good old Yo-yo is the way to do it. Burner on, over the arc and cut the turning circle. A flat turn in the Viggen is not on. This is a super simulation. :thumbup: Cheers. David

Thanks, this explains why my wingman was deaf, I was on easy comms!:thumbup: Is the defective tuning wheel on the fix list? Also we can only assign groups or units to radio attack menu, a runway attack or complete mission radio menu would be nice.;) Cheers.

Thanks again. I have had a much more productive "type training" session today. No surged compressors. Got the Navigation sorted, wp updates, take off and landing in all weather! So to finish off, I put a simple mission together that would test my maneuvering.....Placed a couple of Helis in an orbit around a few hills and valleys. Slash and run, turn and climb, yo-yo and hey this beauty does it all. Just listen to that AOA warning beep and the sidewinders do the rest! Not bad for a mud mover without an internal cannon.:smilewink: Now for some bomb practise! Best $50 I ever spent!:D Cheers! David

Thanks chaps. Copy that Nick, both the AOA and the Airstart being a continuous ignition would make sense and explain why I can't relight properly... My "thumps" (great modelling by the way!....swear my chair vibrates as well!!), are happening at low level, so I don't have much room to lower the nose. This is a serious simulation for sure! I havn't dropped a single bomb yet, just flying and navigating with INS is a real challenge to master.:) I will practise some more. Regards David

After flying this aircraft for a first few test flights, I must say what a superb simulation this is! So impressed was I, I splashed out and bought the Mig 21 as well in the sale:thumbup: The only question (so far) is that I am experiencing a lot of engine surges and subsequent flame outs? I follow the procedures, fly carefully, fuel to manual, to no avail, I can not re light the engine. The re start switch does not appear to work. I know it's probably my high alpha habit I have got into after flying the Hog for ages, but were these Viggens prone to such failures at slow speed/high alpha? If yes, then can the relight be tweaked to work better please? My crew chief says he's running out of parachutes, not to mention aircraft!:cry: Cheers.