LaLa

Yes please! Thanks alot!

Is it possible to export RWR on the F16? I noticed that I have a couple of monitor lua files that dont show up in DCS setup, despite being in the correct folder along with the others...corruption??

I'm modifying my monitor config but cant get the RWR to display. Below my .lua _ = function(p) return p; end; name = _('F16C MCD 3520x1080'); Description = 'f16 setup 2 monitors' --TOTAL DEL VIEWPORT Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 16/9; } } --LEFT LEFT_MFCD = { x = 1920+70; y = 99; width = 642; height = 707; } --RIGHT RIGHT_MFCD = { x = 1920+877; y = 99; width = 642; height = 707; } -- RWR F16_RWR = { x = 1920+711; y = 730; width = 180; height = 153; } F16_DED = { x = 1920+1211; y = 0; width = 317; height = 108; } EHSI = { x = 1920+1418; y = 710; width = 120; height = 120; } UIMainView = Viewports.Center The right and left MCDs OK, the EHSI OK, but cant see the DED or RWR. Any help appreciated.

Maybe can link. I have BS2 purchased in 2016 Thank you Sir: I have BS2 Steam version purchased in 2016, OooopsI just uninstalled it, apparently to link I need to reinstall the Steam version in order to see my license. OK thanx again!

I suspect this is not an option anymore since the KA-50 says NOT Steam compatible. Just checking..... Having both Steam and non-Steam versions of DCS World is taking up too much space on my SSD, so I wanted to move my Steam version key to the non-Steam version. I presently have 3 versions of DCS World, version 1.52, 2.5.x non Steam versions and Steam version of 2.5.x

Tried changing the video settings low, medium, high options makes no difference.

This behavior can can also be seen in A10-C v 1.58. Not exactly the same, but similar.

This issue is related to A10-C. After zooming out from the HUD, the screen zooms back in by itself. This may happen several times before, it lets you zoom out and stay at that point. I usually zoom from mapping on Thrustmaster Warthog joystick that has worked perfectly for years. I believe the same effect was seen while zooming with numpad keyboard, See here, this was zooming out with keyboard not joystick.

ASCII codes for upper and lower case characters are different. Programmatically easy to convert from one to the other, but would appear that Helios only responds to lower case. Look at the captured image from Helios here, while not specifically stating use lower case, Gadroc only shows lower case. Computer programs are very selective/specific unless the author foresaw the problem, and programmed accordingly, which in this case he apparently did not. https://simhq.com/forum/ubbthreads.php/topics/4312967/helios-use-of-send-keys-to-control-dcs-cockpit-design#Post4312967

I see on Steam someone had a similar issue, and found it to be associated with a Windows 10 update. https://steamcommunity.com/app/223750/discussions/2/1744480967008745869/?l=koreana Tried rolling back my updates, (several were completed just today) but it had no effect, 1.58 still doesnt work.

Put my old monitor back, and now DCS A10-C crashes it too.... Not nice!

Thank you but joy there! ;-( Placed a ticket with ED and they said version 1.58...nope too old we dont touch it! ;-( Very disappointing my hardware not good enough for 2.5, just because I upgrade my monitor cant use DCS A10-C anymore.

Just got a new monitor, so I'm running a 2 monitor configuration. As soon as A10-C starts it allows me to login then immediately crashes and creates a zip file. No I havent changed my monitor lua files yet. I wanted to see what if looked like on a single screen first! Any help appreciated!

Rearm Sams Nice collection of data. Just for clarification, does rearm per 2 rearm time 360 Mean if to rearm 4 it takes 720 seconds?

Bingo exactly what I was looking for thank you Feefififum! Grimes did a great job here! Reload times are in seconds, it appears that most SAMs require at >2 minutes, but most 5 or so before ready to fire again, so time to come around again.

Has anyone compiled this info, of SAM's? Does DCS use real reload times? I presume so, any info on this topic. Thanx

Does anyone have a list of what to do when the various warning indicators start blinking. Some seem obvious but, partial electrical failure, engines, hydraulics, oil pressure and fuel flow come to mind. Obviously total loss of is problematic of any system. In the event of engine damage, does damage get progressively worse with time? (fire vs physical damage), assuming no action taken. Does loss of a single generator prevent normal continued power output?

Thank you Habu 69 and Mad Dog IC all good stuff, I suppose there isnt a user template we could modify to prevent continual modifications for every mission. Never mind very helpful anyway! La

Has anyone tried flying NOT using the export LUA or sending and receiving input received from multi-monitors, to see if the vanilla one-screen simple input works? Even if it is a result, who would fly this way! Possible external inputs accessed while in replay corrupts the data, or data rates too high in violent maneuvers for program to cope.

Great idea I didnt know the ME had the ability to set the probability of objects spawning ...cool! Thank you again kylekatarn720

Thank you Wrench that was helpful, I didnt even realize the .miz was a compressed file! Unfortunately I dont think radio presets, that are saved in-plane are written to disk? Too bad that would make things easier.

Great info FlyingPhotog, and kylekatarn720! At this time my questions are related to training, and not the way I would fly a mission, if I were attempting to simulate an actual flight. Information is all good, whether used in actual mission or not, it requires judgement to determine if the action is appropriate under the circumstances. While attacking SAM's may not be a action usually undertaken by A10's doing so is not without value in terms of learning ranges and factors unrelated to the statistics regarding a weapon capability. For example when I watch my attack of Zu-23s I noted how they require a couple of seconds to rotate around to your direction, seems to me that a couple of seconds is often the time window that determine if you hit a target or are hit by it. Its great to get this kind of feedback from the DSC community! Thank you!

I'm looking into some programming radios, and I wondered is there a way to get or set the initial radio frequency programmatically either before or after a mission start? I dont want to have to look in-plane for the present setting, but once I either set programmically, or determined from a variable, I've got a green light. Sure, if the mission breifing uses a frequency, but how to get that value from the .miz file.

Thanks a lot wrench, your pictures seem to show about the same level of detail as the current Caucasus maps in the TAD... too bad I had hope for better resolution, at least as good as Skyvector's VFR charts. Thanx again for your submission.

Thank you kylekatarn720 and FlyingPhotog, all good info for the noobie. With regard to mission preparation prior to flight, yes, given proper resources (detailed topos marked with significant mission details ie threats, waypoints, easily identifiable man-made or geographic features) makes situational awareness easier while targeting and avoiding threats would help a lot.) Something I havent researched yet os the use of the knee-pad for use of pre-flight intel ie maps etc, but I spose that neednt be incorporated into pdf's for use in flight. With regard to searching out the window, how is a search conducted? Are markpoints created to create a path to plan out where to search, to prevent too much overlap or inefficient random searches? Regards LaLa