JG14_Smil

Thanks, but there is nothing to save. Enter a cold 109 cockpit. Note how DCS AFN2 looks. Note how Ikarus AFN2 looks. Not the same.

I didn't take a flight. I am using the take off instant mission and I noted the gauges that did not work the same as in DCS. The Ikarus AFN2 does nothing, the DCS AFN2 horizontal needle goes to the bottom of the scale, it does not stay centered.

Wind moves the vertical stabilizer the most when at slow speed. Wind from left, right rudder to stay straight, bank left to line up. But.. don't over do it. Wait until the last second before touch-down. Crab your way in.

Outstanding Bad_CrC!! Looking forward to hearing how much I will want to get one. I've been at a crossroads with my PLP setup and it might be the way I go too.

Thank you Tomcat97 for that English manual. I was wondering how I was going to get around the German-only manual. :)

Thanks so much for you fast response! I've never used the AFN2 for ILS, but I note that the horizontal needle doesn't move, it should go to the bottom of the scale when I start the 109. Could be an initialize thing again.

Yes. No problem.

sobe: You can just go Ikarus configuration tab, click on front panel detail, replace background .png file with a -, transmit, save. close cockpit, show cockpit. Have the background be on your main monitor and edit the gauge where you want it. Delete the gauges you don't want. I think this will do what you ask. Whether it will do what you want? You have to find out.

Hello, I don't know much about the module but I have found two bugs in the 109K Ikarus profile. I've not been able to affect them with my usual putzing around. The HSI and the AFN2 landing assist do not operate like the DCS gauges. I think there might some initialization thing not working correctly as the fuel gauge does not reset and the HSI wont work at all until I change the heading command. You need to change the heading command to note the different behavior of the HSI.

Very interesting you got Ikarus to work without being the last line.

Empty that folder regularly.

Try posting in the Ikarus thread. Might get some help from someone smarter than I. :) https://forums.eagle.ru/showthread.php?t=179525

-- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[scripts\DCS-ExportScript\ExportScript.lua]]) intelliVIBE = true local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[scripts\DCS-SimpleRadioStandalone.lua]]) Here is everything in my export.lua. I think line 1 is for SRS, then my obsolete feedback seat, then Ikarus last.

Hello Sully. I really don't know, but I do note my export lua line is: local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[scripts\DCS-SimpleRadioStandalone.lua]])

Glad it is working Gary. Actually, I find 2.1 to have better performance than 2.0. My Normandy and NTTR run the same. I find Normandy to be kind of boring and don't spend time there, so I don't really note performance details like I do in NTTR.

Black knob is just a hat switch. I used one from an old Suncom in my Ka-50 collective. Buying milsurp is just not my approach to building, but Patriot has you covered. :) Good luck with your build!

I think you would just need a clear background.

Hello MRaza, Confusing as heck, but click on the plus sign icon. Took me a bit to find it.

Gary, if you have saved games folders from a previous build, be sure to do the rename routine: Rename the saved games folders, start DCS (let it run in a small window), click instant mission, fly, close, exit. Move config files from the renamed folders back into the new saved games folders. Can do wonders.

I'm pretty impressed by the 378.66 in both 1.5 and 2.1. I found it similar to 368 drivers in performance. I run multi monitor and use in-DCS MSAA and AS at 8x, 16x. I now use HDR in 2.1 also and it looks wonderful. I would need a bigger CPU for differed shading.

It is a shame that Helios is not updated even though the open-source code is there. The latest profiles are work-arounds made from original profiles and don't allow all the great features of the Helios editor to be used for customization of a profile. Capt Zeen did such great work on these new profiles! Artwork is scripted into place and you have to look through the files to see which artwork you want to make a cut-out section. I'm sure he'll be along to help when he gets a chance. I know nothing of making artwork. I've begun to work on a L-39 module for Helios. I can see where certain data goes and hope that someday someone could finish and then compile the L-39 module into Helios. Please let me know if there is any support for this. Isn't this what open-source code is about? Another cool thing to have would be Capt Zeens artwork compiled into a DLL so it can be used in the Helios editor to make customized profiles from scratch. I miss Helios and my Phidgets LED and servo controllers. Best wishes,

Tired of editing hehe. Please note DCS is pretty unforgiving on LOS and radio signals. If your beacon does not show up, it might be masked by terrain. This can be improved on with the middle position number, but it should be done in a way that is not a cheat (you can make the beacon come in at all times, but real world is not like that). good luck with your editing and learning! I love flying the L-39 using these RSBN and PRMG edits in the NTTR. PRMG works much better than in 1.5. RSBN Glideslope mode does not work as well in the NTTR. It will fly you into terrain. Switch to Landing mode about 50 KM from runway for RSBN and PRMG glideslope to intercept.

You can leave the scene object line alone or comment it out. Beacon will still work. If world_38 is the last beacon in line, and you make a new one it would be 'world_39'. (there are only 40!) How to get position numbers? Edit one and see where it goes. Use mission editor to see where it went. I *believe* it is: north/south, up/down, east/west. Make sure frequency and channel match. channel 16 is '816000000' edit the '16' to your new channel on both. Please note channel 16 is Daggett beacon. Sometimes Mission Editor is the only way to see these beacons. ILS only show up in the editor. Do not do ILS testing while in the ME, it won't work correctly. Export the mission, then run it for it to work correctly.

no. Middle number is height, I believe. If you lower it beacons will be hidden by terrain more, less if you raise this number. Last number moves the beacon ease/west (I believe). I think first number is north/south.

I would love to sit with someone and go through the front/back seat issues. I'm not wasting any more time on reporting bugs, but I would like to know what works and doesn't. You can learn a lot about what is what by looking at the mainpanel_init.lua file. Last two times I tried letting someone fly, both of us just freeze in position while the sim keeps running.