JG14_Smil

Groom Lake bug found and squashed. Shared frequency caused PRMG to line up with the RSBN. Changing PRMG channel to 19 makes it work perfectly. { display_name = _('Groom Lake 32 PRMG 20'); beaconId = 'airfield2_3'; type = BEACON_TYPE_PRMG_GLIDESLOPE; callsign = 'GML'; frequency = 819000000.0; channel = 19; position = { -290061.156250, 1369.163234, -86409.328125 }; direction = 156.426864; positionGeo = { latitude = 37.220000, longitude = -115.787349 }; --sceneObjects = {'t:93585410'}; }; { display_name = _('Groom Lake 32 PRMG 20'); beaconId = 'airfield2_4'; type = BEACON_TYPE_PRMG_LOCALIZER; callsign = 'GML'; frequency = 819000000.0; channel = 19; position = { -286660.593750, 1357.831924, -87720.343750 }; direction = 156.426878; positionGeo = { latitude = 37.250797, longitude = -115.801637 }; --sceneObjects = {'t:194117769'}; chartOffsetX = 4269.000000; }; This makes me wonder if some RSBN frequencies are incorrect and thus not giving proper RSBN Glideslope. Will look into that.. Have not updated the file with this as it is an easy edit. PM me if you need me to post the new file.

Please note: Groom Lake ILS has a line up issue and does not work correctly yet. Trying to find out why. Flying around testing takes time as I fly online. If you should see any bugs, please let me know.

Typo bug, Silverbow RSBN (Tonopah). { display_name = _('Silverbow'); beaconId = 'airfield18_9'; type = BEACON_TYPE_RSBN; callsign = 'TQQ'; frequency = 829000000.0; channel = 29; position = { -227436.906250, 1689.104961, -174559.000000 }; direction = -24.171670; positionGeo = { latitude = 37.790475, longitude = -116.779233 }; ---sceneObjects = {'t:209715232'}; }; This RSBN shared channel 28 with Creech. I changed Silverbow to channel 29. I did not update the posted file with this, so let me know if you would like the new version.

One more typo. { display_name = _('BoulderCity RSBN'); beaconId = 'world_37'; type = BEACON_TYPE_VORTAC; change it to BEACON_TYPE_RSBN;,; callsign = 'BLD'; frequency = 815000000.0; channel = 15; position = { -424440.156250, 1080.227277, -1424.503052 }; direction = 41.253552; positionGeo = { latitude = 35.995752, longitude = -114.863607 }; --sceneObjects = {'t:131138221'}; };

Found a typo. McCarran RSBN works as RSBN channel 20, same as Groom Lake. You can fly with it like this and the needle will switch automatically or edit: { display_name = _('LasVegas RSBN/VORTAC'); beaconId = 'airfield3_9'; type = BEACON_TYPE_RSBN; callsign = 'MAC'; frequency = 825000000.0; (red five was a zero) channel = 25; position = { -415686.093750, 656.234299, -28303.363281 }; direction = -179.199384; positionGeo = { latitude = 36.079576, longitude = -115.159816 }; --sceneObjects = {'t:138676547'}; };

Syntax has changed in a recent update! I went through and have the same mods as before with RSBN and PRMG. Every random test I have done shows it all working correctly now in 2.1.1.6837. Please note I did not add any NDB and Inner/Outer markers yet. I know I don't use them much but I will add them at later date. Same as the original modded file. I want to test what is here first. Only downside I know of from this file is in the ME. The mods are over-laid on the original beacons and they can be hard to read. Does not affect when in MP F10 view. There was/is an error line in the log file, but it is from the original ILS and not the modded beacons. Taking the file down until I test everything. It may be a while.

I think it always uses KM, even if Imperial.

I have started work on a version 2.1.1 beacons.lua and I'm getting properly working PRMG/ILS again. It could be something has changed. I have Nellis 21L, McCarran 25L, 25R working correctly now. I am testing each PRMG as I mod it, verifying all channels and ID's. I've encountered an angle error at Groom, but I hope to get all airfields with ILS working again today.

Please note, 25L channel 26 is same as Tonopah test Range runway. It will work with same channels as the distance is far apart, but I edited 25L to be channel 24 in my version. { name = _('McCarran'); beaconId = 'airfield3_7'; type = BEACON_TYPE_PRMG_GLIDESLOPE; callsign = 'MCL'; channel = 24; frequency = 824000000.0; position = { -416373.156250, 631.500261, -25578.058594 }; direction = 89.345650; positionGeo = { latitude = 36.072917, longitude = -115.129710 }; --sceneObjects = {'t:137300408'}; }; { name = _('McCarran'); beaconId = 'airfield3_8'; type = BEACON_TYPE_PRMG_LOCALIZER; callsign = 'MCL'; channel = 24; frequency = 824000000.0; position = { -416353.000000, 662.919620, -28740.046875 }; direction = 88.846008; --88.846008 positionGeo = { latitude = 36.073641, longitude = -115.164803 }; --sceneObjects = {'t:71240604'}; chartOffsetX = 3623.000000; };

.

Yes, same here.

.

Just did a system reset. Let me double check... probably grabbed the wrong file.

I've ridden in the back of a Hawk before... has it been disabled?

.

Sheesh! Thanks Big Newy!. I was using the serial I gifted to Capt Zeen.

Hawk yes, C-101 No.

Hello, I had to redo my system today. Clean install of Windows 10. I de-activated all my modules before I reset the computer. I downloaded and installed the 1.5 build and then used module manager to install the L-39. When DCS restarts, I get a red message saying my serial number is invalid. It is my proper serial number from my account and I have tried redoing the process several times. I did note it said I had 8 activations left and not 9. If I could be steered towards a fix for this I would be very grateful.

Back in the day, guys found that the more you sharpened graphics, the harder it became to see a dot. Still applies. Spotting contacts is near impossible in DCS (IMHO). Harder than any other sim I've been in. I'm glad I retired from combat. :)

_ = function(p) return p; end; name = _('1 Screen'); Description = 'One monitor configuration' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } You would edit x and y values. 0,0 is top left corner of monitor that is furthest to the left. Note you may have to enter exact values for width, height and aspect ratio. DCS uses variables by default, ie.- "screen.height" can also be 1080 or whatever your monitor resolution is.

Edit the multi monitor config lua file and give the position you want it to start. You most likely start at 0,0 now. The numbers depend on how your desktop is setup.

I can't imagine how hard it is to build a simulator of this scale. As for your answer? No. (IMHO) Bottom line is the next update will bring some new features and some new bugs. Some bugs will get fixed, some won't. If the sim was ported to the latest and greatest coding, there would just be different bugs. This is my twenty-third year of doing this and I have learned how things are. I still manage to enjoy DCS. quit wishin', go fishin' :)

AF typo. Sorry Water always impacts performance. The water runs under the entire map, even though you cant see it. Not sure if it is the same in the NTTR.

Hello Gary, DCS is updating now and settings GUI will change a bit. Screenshot will have to wait. My monitor setup and the fact that the only thing I see of the DCS L-39 cockpit is the canopy rail and mirror make my setup unique. The mirror is near useless, so I run 256 res in the cockpit. I can run 1024 every frame, but there is really no point to doing so. Deferred shading and my PLP monitors don't go together well (I cant go full screen 3D), so any eye candy updates to DCS aren't useable for me. Instead I run 8x and 16x MSAA and AS. Actually looks great. I don't see that ever changing as DS and in-game AS and MSAA are never going to work together (documented about DS). Other than that, HDR is the only notable thing I use. If you want smooth flight, you need to turn that water to low. I know you said you don't want to though. It would be great if there was a hotkey to toggle this option for when you wanted it and not. waiting to see what new adventure this update will bring...

Hello, No complaints with the 378.66. Any stutter or lag is DCS related. Win 10, i7-3770K@3.5Ghz, 8 gig ram, Titan gfx card.