Maverick-X

looks exactly the same, except some images I want to import don't show up. As you mentioned screenshots: I have some in the same folder, they do show up. The images I want to add are jpg aswell, just no screenshots but taken with the windows snipping tool and then edited and resized with Gimp. But I fail to see why this should affect the selection dialogue / the appearance of the pictures...

I hope this is as simple and stupid as I think it is: I want to add a picture for the mission briefing, but I can't select that picture. It is a 512x512 px *.jpg. I tried bigger and smaller resolution, but they still don't show up in the "choose picture" dialogue. Thx, Mav

If I remember correctly, I had the same issue after 1.2.7, where I simply did not have the command to bind. Deleted the config files for the FC3 aircraft in savedgames folder and then DCS recreates them with default setup and all commands that should be available

I don't see the downside, but its your server ^^

Hey, would you mind stating a reason? I always liked to fly phantom scythe for example when the server got a bit more crowded, I guess a set password will reduce the number of players.

views perhaps are disabled in the mission you are flying.

Don't have time right now to read the whole thread, so this is perhaps already mentioned, but I want to throw in my two cents: When you get engaged by AAA and spot them visually, try to remember their location in reference to landmarks like villages and rivers. Then break away, turn back in and fire the maverick. Main thing is reaquireing the target after the turn, ofc. I guess only training will get you ahead with this tactic. The TGP is quite useless at these ranges. For target search I find 20nm is a good distance to possible target location. If you have them almost on spot 10nm will work, but any closer only the good ol' mark1 eyeball will work for efficient target aquisition. The zoom feature really comes in handy! (and headtracking like TrackIR ofc) To the overall Issue of being engaged by AAA: you fly to low! You can only risk getting that low when you are sure to have destroyed all antiair assets or know of their existence and decide it is a reasonable risk to take. Go low and have a strela there, chances are good you end up at least as a mission kill.

I'm in if I can make it in time. Ka-50/Su-25T prefered ...found the sign-in-sheet

stay stationary sounds like a bad advice to me, doesn't that make you an easy target?

I'm not sure if this is helpful, but I often run into WPTS for targets that are set on 16000ft for example. I change the WP elevation by going to the CDU-WP-Page and select waypoint. The desired WP has to be selected, thats OSB 19 or so. After startup the WP-Page should show WP 0. I then enter 0 for that WPTS elevation and then it is changed, and for this waypoint only. Never ran into changing all waypoint's elevation data.

I ran into another issue with exporting displays of the A10: After exporting the MFDs I tried to export more displays, which worked fine except for the CMSP. Monitor Config _ = function(p) return p; end; name = _('Mav_CougarMFD2'); Description = 'Right MFCD on the right and camera on the center' function default_setup() Viewports = { Center = { x = 0; y = 0; width = 1920; --screen.width; height = 1080; --screen.height; viewDx = 0; viewDy = 0; aspect = 16 / 9; } } Gui = { x = 0; y = 0; width = 1920; height = 1080; } UIMainView = Gui end default_setup(); UIMainView = Viewports.Center; function reconfigure_for_unit(unit_type) if unit_type == 'Ka-50' then Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 16 / 9; }, } RIGHT_MFCD = { x = 2812; y = 0; width = 788; height = 1050; viewDx = 1; viewDy = 0; aspect = 3/4; } LEFT_MFCD = { x = 1920; y = 0; width = 840; height = 630; viewDx = 0; viewDy = 0; aspect = 4/3; } elseif unit_type == 'A-10C' then Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 16 / 9; } } LEFT_MFCD = { x = 1920; y = 0; width = 390; height = 390; } RIGHT_MFCD = { x = 2370; y = 0; width = 780; height = 780; } CDU_SCREEN = { x = 3220; --3210 mfd coordinate y = 70; width = 380; height = 285; } CMS_SCREEN = { x = 1945; y = 460; width = 400; height = 84; } RWR_SCREEN = { x = 1945; y = 625; width = 400; height = 400; } elseif unit_type == 'Su-25T' then Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 16 / 9; } } RIGHT_MFCD = { x = 2060; y = 0; width = 1400; height = 1050; } else default_setup() end endCMSP_init.lua dofile(LockOn_Options.common_script_path.."devices_defs.lua") dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") indicator_type = indicator_types.COMMON purposes = {render_purpose.GENERAL, render_purpose.HUD_ONLY_VIEW, render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- set purposes to draw it always try_find_assigned_viewport("CMS_SCREEN") dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON opacity_sensitive_materials = { "font_CMSP" } -------PAGE IDs------- id_Page = { PAGE_NULL = 0, PAGE_OFF = 1, PAGE_MAIN = 2 } id_pagesubset = { MAIN = 0 } page_subsets = {} page_subsets[id_pagesubset.MAIN] = LockOn_Options.script_path.."CMSP/indicator/CMSP_page.lua" ---------------------- pages = {} pages[id_Page.PAGE_MAIN] = {id_pagesubset.MAIN} init_pageID = id_Page.PAGE_MAIN --purposes = {render_purpose.GENERAL}

This whole plug and play thing for the hog is nice and all... but what if I want to customize that? I don't want to install TARGET just for the MFDs... but I'd like to change some assignments, which I can't because everything except the L/R-MFD-Buttons are greyed out. Is there any solution?

Hey, I've got a simmilar problem with greyed out fields in the GUI. Got CougarMFDs and wanted to reassign the rockerbuttons (thought STP would be better than brightness... I tried resetting the keyassignments but that did not get me access to the greyed out parts. I'd prefer not to get TARGET, as I already have profiling software for my Mouse, Keyboard and Joystick... each -.- Is there a config file I can edit to add the wanted funktionality? I took a look in savedgames\DCS\config\input... but there is no file regarding the MFD's

If there are no threads to you, you could aswell simply hover 4-8km away depending on the weapon you intend to use. You are safe from being engaged by the enemy except from atgm's perhaps, which are easy to dodge even from a hover. Might be a fun thing to master, but I don't think it is effective. I'll give it a try though, as I'm curious how hard it is to maintain speed and distance

I ofc read what you wrote, I simply disagree with you. I might not be able to convince you, but as long as there is a way to get your aircraft trimmed to a new state of flight you should. If there really was no reasonable way to set a satisfying trim I'd agree to just skip that, but there is, so do it! Perhaps I'm phrasing this a little to strict... If you have a very light roll or pitch change with centered stick it's nonsense to try and trim this, but in any larger or lets say annoying rate trim is the answer

You're welcome. Another short hint regarding the SPI: you can see your SPI on the TAD, it is represented by the weddingcake-symbol. (white-outline symbol that looks like a multilayer cake). You either see it in the current waypoint/markpoint symbol or around your TGP marker. China down long resets SPI to Steerpoint.

I understand the Issue with the current SFM trim, but not trimming the aircraft can't be a reasonable approach! I don't think hack is the right term, as there is nothing to be modified in order for it to work. Furthermore it is a very good work around for the great SFM trim system. I perhaps get the term "minute correction" wrong, as I'm not 100% sure what you mean with that. Basically you trim your aircraft for every new flight state: you change your speed, altitude or both -> retrim the aircraft so controls are neutral again. For correction I understand correcting my current attitude, which would not be something to be done with trimming. In general you can't argue that >always trim< is simply a basic rule of flight. A bug in a simulator might make trim uneasy or even impossible, but that does not change basic rules of aviation, even more so as there is a workaround to get a working trim. Trimming makes life easier, especially for a hard task like carrier landings. It might be a bit too easy with exploiting the autopilot, but attempting to land a badly trimmed aircraft on a carrier is a no-go

Its an overall excellent advice. Trim in FC3 is... lets say special. best way to achieve a well trimmed aircraft in fc3 without fiddling around with the trim for 30 mikes is switchung on/off attitude control autopilot. That said I'd still stick to >always trim your aircraft<

Thanks, I tried that. Found nothing and ended up rewriting the file. Got a working one now ^^

All trimming does in a flight sim is recentering the stick, so you have a neutral position of the stick for your current flight state. "Don't trim" is pretty much the worst thing you can tell anyone, anywhere. regardless of simulator or real pilot. ALWAYS! trim the aircraft in a new state of flight!!! As for approach speed: The speed does not matter at all. Its all about angle of attack (AoA). You will have a higher AoA at the same speed if your weight is higher, the AoA is extremely important for carrier landings as it indicates your Eye/Hook value. That is basically the difference of cockpit height to arrestor-hook-height. Your approach may look right, but if your pitch is too high your hook is too low, resulting in an air-hook if you wave off your approach. If your pitch is too low your hook ends up to high and will not hit the arrestor cable. So the correct AoA gives you the correct Eye/Hook (pitch) and also the correct speed for your current weight in order not to get too close to the stallspeed.

I don't think that is a suitable method for flightsims. That works great in casual shooters, but if its not the close range to the enemy that brings you in trouble, than the systems limitation of your weapon systems. I guess you could get some shots of with rockets, but you usually want forward motion w/o any sideslip and a dive for this, so you wont be accurate. You can completely forget vikhrs, as they are beamriders and need to stay between target and launchplatform. ...and then there still is the Danger of close range. An AK47 is enough to ruin your shkval...

TMS forward long will make your TGP (if SOI) SPI, otherwise your waypoint will be SPI, this is why your Mav is slewing to the WP instead of your TGP-Target. TMS forward short is then used to accuire lock with the Mav. If it doesn't lock you are too far away, just try again.

I tried to write a lua file that gives me different configuration for the A10C, Ka50 and Su25T, but this file is not recognized in the options menu. I guess that is due to incorrect lua code. I'd be glad if someone could give me an example for the framework of a file that includes sets for two different aircraft. If someone is willing to have a look on my lua file, I already posted it here: http://forums.eagle.ru/showthread.php?p=2024859#post2024859

Hey, I've tried to create a file with different setups for different Aircraft, but something seems to be wrong with the lua-code as it doesn't show up in the option-dropdown-menu. Resolution shouldn't really matter as this is a first test... but in case it does: 1920*1080 left + 1680*1050 right, so 3600*1080 in total. Would be great if you guys could take a look at my code, as I'm not very experienced with lua-coding (or coding in general): EDIT: Guess I found some erroneous brackets, but it still doesn't show up

Didn't think about configuring them that way. Sounds good. I already use the keyboard for cdu-input, although I found out about that feature much later than I'd like to admit xD Thats an issue I havent really thought about. I really should have as I only own a GTX460 (but overclocked). Guess I should do some tests before buying a Screen that kills my performance. But I'm pretty convinced of the Cougars by now ^^