Opy

Happened to be testing it out last night and took a pic. The full travel is huge, maybe 28cm between axis extremes at top of stick. Roughly 30 degrees from centre. I tried it between my legs and just kept hitting myself at about 80% pull back. If I were to mount it there, I think I'd raise the base 15-25mm to ensure leg clearance. Though you can just make it more sensitive, so physical 80% movement equates to 100% in game. As a side note, the cable extension I received with it (last week) is no longer a cable, but a solid rubberized length. The connector was also turned 90 degrees, which is fine with the loose cable of the Virpil flight sticks, but not good for the hard mounted Warthog stick connector. You can see it dwarfing the full sized keyboard and 24 inch monitor.

Not something I've noticed on the trigger. Sounds like something sugary (think cordial or fizzy drink or coffee) was spilled in there somehow. Other than that, no idea, sorry.

Haha, good one SV. I hope to try out VR one day, but I'd like a system with an above average gap that I can easily look through to access the physical controls that I've already setup. Lower immersion, but I like my switch panels and mfds. Kind of want the best of all worlds. And a new house.

I guess it would need to save the data from the mission into the save. You can delete the miz file in Windows, so it wouldn't check if there are saved games relying on it.

Ah yeah. There is a setting to sync controls which would alleviate the issue. Used that for a while. Forget what made me turn it off, must have been something I forgot to reset each time. Flaps is a very likely one. Now that I have the Logitech Switch Panel, all hell could break loose if I start airborne and everything is set to 'off'. (While I think of it, testing right now...and it's safe, only HOTAS controls are synced) If you use the throttle in other games, the switches could be anywhere if you forget to reset them. Still, it is worth trying it out for yourself. May reduce more frustration than it causes. To turn this on, from main menu screen, go to: Options - Misc - "Synchronize Cockpit with HOTAS Controls at Mission Start" (Haha, continued to fly the mission I loaded for the above testing. When I had a SAM launch at me and reached the thumb over for countermeasures, I realised I had forgotten to change flightsticks. Virpil stick has a button there, not the 4+1 of the TMWH)

Haha, I'm already running out of excuses for my lack of skills, don't take more from me, Wrench !

Any movement will do. It's a little less effort if throttles are already above zero, as GTFreeFlyer says, but if you start with them already down in the cut off area, you just need to lift them, push forward and pull them back. I try to do what GT is saying before loading in, but my memory and my self discipline were left at a bar somewhere in my 20's.

Just for a laugh at my expense; I've had the TMWH duo for longer than I can remember. Always had trouble with the startup sequence too. Only a couple years ago I realised that you can lift the throttle levers up to pull them into the cut off area. So much easier! I was by myself at the time and burst into hysterical laughter at such a simple oversight. Then again, I think it was only last year that I discovered the nose wheel button doubles as the laser. Doh!

Try Youtube for some great tutorials. 20 minutes there can save you months of frustration. I'm kind of the opposite, CCIP hates me. Mostly lack of experience, partially lack of trim or plane deciding that nose down would be more fun if it turned right at the same time. Autopilot helps, you can micro adjust, but it feels like cheating. Somehow, LGBs are often very inaccurate for me on CCRP. GPS guided are great. Clusters are hard to tell because it doesn't really matter. Not practiced iron bombs in ages but I think they were okay. Some weapons are terrible from altitude too. If Youtube doesn't help, make your question a bit more specific. What are you trying to drop? Are you trying to set target then turn in and attack or giving yourself a long line to target to have time to setup your target and attack in the one run? (Sounds like the 2nd option) (Oh, and savour this heat, Summer is not here for much longer....)

No experience with them. I expect they would be less comfortable than a wider set after some time.

This is a great unit. Well designed with the cabling channel in the back too. Though the screw holes are quite small so I had to drill them out to put bigger screws in when I attached it to the removable frame https://forums.eagle.ru/showthread.php?t=228355 The 6 buttons that are not in game (below the Warning light) I mapped to the fire handles and the start up checks (Signal, Fuel, Oxygen). Considering replacing fire handle mappings with T/O Trim, Anti-Skid and Uncage SAI. Yeah, may do that tonight.

Seems to be fixed now. Added the below to the end of the AN_ALR69V_init.lua file. This is the only modification I need. -- Code below is used for the rendering when no viewport has been created purposes = {render_purpose.GENERAL, -- Rendering in 3D View render_purpose.HUD_ONLY_VIEW, -- Rendering In HUD only View render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, -- Rendering in External View render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- Rendering in In cockpit view but NOT in 3D cockpit -- End of rendering configuration dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("ED_A10C_RWR") And in my monitor setup file, I called it ED_A10C_RWR, this was mostly just due to a pile of experiments.

I don't think this is a file corruption now, as I get the same thing on a 2nd installation. Any attribute changes I make to the above AN_ALR69V_init.lua don't seem to make a difference. Hopefully I'll fluke something tonight and get it right, but really scratching my head at this one.

Sorry to be another one calling for help. I've setup RWR a number of times before, but this is the first time I've seen this. It is small and wont move from the top left corner, 1,1 (see the red circle). My monitor setup file is set so it should appear in the blue circle. Any idea what files may have corrupted for this to happen? Here is my monitorsetup file, maybe it's as simple as renaming RWR_SCREEN ? --***DO NOT MODIFY THESE COMMENT LINES*** --A10CVirtualCockpitServer v0.0.0.0 --LOCATION Config\MonitorSetup --HOOKTO --Monitor lua _ = function(p) return p; end; name = _('A-10C Virtual Cockpit Server'); Description = 'Setup for A-10C Virtual Cockpit Server MFCD and CDU Exports.' Viewports = { Center = { x = 0; y = 0; width = 3968; height = 2131; viewDx = 0; viewDy = 0; aspect = 1.8620366025340215861098076021; } } LEFT_MFCD = { x = 1086; y = 1287; width = 359; height = 359; } RIGHT_MFCD = { x = 2528; y = 1277; width = 359; height = 359; } CDU_EXPORT = { x = 2944; y = 1438; width = 280; height = 180; } RWR_SCREEN = { x = 1706; y = 1287; width = 300; height = 300; } UIMainView = Viewports.Center I don't recall having to change the AN_ALR69V_init.lua this much previously, but it did get the RWR to at least appear on the screen. (From icemaker's post 8 years ago) dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON -- Code below is used for the rendering when no viewport has been created purposes = {render_purpose.GENERAL, -- Rendering in 3D View render_purpose.HUD_ONLY_VIEW, -- Rendering In HUD only View render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, -- Rendering in External View render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- Rendering in In cockpit view but NOT in 3D cockpit -- End of rendering configuration screenspace_scale_initial = 3; screenspace_diplacement = {0,0} local x_size = 1 local y_size = 1 function update_screenspace_diplacement(zoom_value) screenspace_scale = screenspace_scale_initial + zoom_value; if screenspace_scale < 1 then screenspace_scale = 1 end local screen_height = 2.0; local screen_width = screen_height * LockOn_Options.screen.aspect; local scaled_width = SelfWidth * screenspace_scale local scaled_height = y_size * scaled_width -- for indicator all sizes is function of width scaled_width = x_size * scaled_width screenspace_diplacement = { 0.5 * screen_width - 0.5 * scaled_width, -0.5 * screen_height + 0.5 * scaled_height} screenspace_diplacement_arcade = {screenspace_diplacement[1], 0.5 * screen_height - 0.5 * scaled_height} end update_screenspace_diplacement(0) function set_full_viewport_coverage(viewport) local w = LockOn_Options.screen.width local h = LockOn_Options.screen.height local a = LockOn_Options.screen.aspect local x = (-1.0 + 2.0 * (viewport.x / w)) * a local y = 1.0 - 2.0 * (viewport.y / h) local width = (viewport.width / w) * a local height = viewport.height / h local scl_hgt_K = y_size * SelfWidth -- size always function of SelfWidth local scl_wdt_K = x_size * SelfWidth -- size always function of SelfWidth screenspace_scale_x = 2.0 * width / scl_wdt_K screenspace_scale_y = 2.0 * height / scl_hgt_K screenspace_diplacement = {x + width, y - height} screenspace_diplacement_arcade = screenspace_diplacement -- The code below is used for rendering When you use viewports comments are same as above for rendering purposes = {render_purpose.HUD_ONLY_VIEW, render_purpose.GENERAL, --Uncoment this line by removing the "--" to render in 3D cockpit. render_purpose.SCREENSPACE_OUTSIDE_COCKPIT, render_purpose.SCREENSPACE_INSIDE_COCKPIT} -- set purposes to draw it always -- End of rendering configuration render_target_always = true end -- try to find assigned viewport local multimonitor_setup_name = "Config/MonitorSetup/"..get_multimonitor_preset_name()..".lua" local env = {} env.screen = LockOn_Options.screen local f = loadfile(multimonitor_setup_name) if f then setfenv(f,env) pcall(f) local vp = nil vp = env.RWR_SCREEN if vp ~= nil then dbg_print("ok we have directly assigned viewport to CDU\n") set_full_viewport_coverage(vp) end end ---------------------- rwr_symbols_bound = 0.027 -- coeff to limit indication on RWR when symbol can't be place on RWR entirely -------PAGE IDs------- id_Page = { PAGE_OFF = 0, PAGE_MAIN = 1, PAGE_BIT = 2 } id_pagesubset = { COMMON = 0, MAIN = 1, BIT = 2, } page_subsets = {} page_subsets[id_pagesubset.COMMON] = LockOn_Options.script_path.."AN_ALR69V/Indicator/AN_ALR69V_COMMON_page.lua" page_subsets[id_pagesubset.MAIN] = LockOn_Options.script_path.."AN_ALR69V/Indicator/AN_ALR69V_MAIN_page.lua" page_subsets[id_pagesubset.BIT] = LockOn_Options.script_path.."AN_ALR69V/Indicator/AN_ALR69V_BIT_page.lua" ---------------------- pages = {} pages[id_Page.PAGE_OFF] = {} pages[id_Page.PAGE_MAIN] = {id_pagesubset.COMMON, id_pagesubset.MAIN} pages[id_Page.PAGE_BIT] = {id_pagesubset.COMMON, id_pagesubset.BIT} init_pageID = id_Page.PAGE_OFF use_parser = false --- master modes A10C_ALR69V_OFF = 0 A10C_ALR69V_MAIN = 1 A10C_ALR69V_BIT = 2 ------------------------------------ pages_by_mode = {} clear_mode_table(pages_by_mode, 2, 0, 0) function get_page_by_mode(master,L2,L3,L4) return get_page_by_mode_global(pages_by_mode,init_pageID,master,L2,L3,L4) end pages_by_mode[A10C_ALR69V_OFF][0][0][0] = id_Page.PAGE_OFF pages_by_mode[A10C_ALR69V_MAIN][0][0][0] = id_Page.PAGE_MAIN pages_by_mode[A10C_ALR69V_BIT][0][0][0] = id_Page.PAGE_BIT opacity_sensitive_materials = { "font_RWR", "INDICATION_RWR" }

I wish I did not watch your video. I've spent way too much money in the past 8 weeks. And now I want to spend a lot more on pedals I don't need! They look very cool. I was curious as to how good they were. You make them sound awesome. Grrrr. Think I'll give my wallet to a family member for safety. Thanks for sharing this build and review vid.

Something I've been wanting to point out for some time is to do with the Cougar MFDs. They are fabulous items, but not quite right for the A10. They have rounded inside corners, where the Warthog has square corners. This causes minor issues with setting up your MFDs and trying not to hide the screen corners. The button positioning is also a little out. I also wanted to see it they could be mounted in a way to make them thinner. It turns out that both these issues are beyond my abilities to resolve with modifying the Cougar MFDs. The circuit board cannot have those inner corners shaved down to square. And taking the back panel off, with hopes of mounting the thicker front onto my frames proved a little difficult as components sit proud of the front frame. I could cut recesses into the wooden frame to accommodate these electrical components, but not worth the effort for now. And this seems a tad overkill:

This is not Simpit Pr0n. This is embarrassing compared to the effort put in by many people, but I don't have space and I need to be able to use this desk for work. For years, I've been using self-adhesive velcro for removable MFD panels. Always leaves that little black rectangle on the screen where you can't see and you can't read if Emperor Palpatine is telling Luke to 'Die' or if he's just calling Luke a 'D..k'. So, on a stinking hot Sydney Summer day, I went and sweated like a waterfall in the workshop. This single contraption holds everything firmly in place and can be slid off when I need to use the screen for other purposes. All of this it just made from timber offcuts. Starting with the end result, all painted black to be not noticeable at all; Unpainted and not yet countersunk a few screws Screws have been countersunk here, so just needed paint at this point. Test fit was more snug than I thought it was going to be, which is great. There is no wobble at all. The rear view. Incidentally, that Vesa mounted stand was made a few years back out of an office paper tray. And finally, my Christmas present, hideously labelled but working well. This is mounted on a mostly chipboard stand, and held solidly in place with a wood working clamp. So is easily removed too. Go back to the top for the final result :) It's my birthday in 24.25 hours, and I've asked the family to buy me a PCI-e SSD card. DCS will run from that very soon. Giggity. Have a great 2019 everybody !

Doing searches to see if anyone has mentioned speed after having lost an engine and this thread looks closest. I lost an engine and found it incredibly hard to stay above trees. (It's alright, found the engine, it just fell between the couch cushions) I had believed the Hog was more than capable of flying with 1 powerplant and the sim was a bit unrealistic in this sense. But reading here, I am thinking that my problem was that I was still fully loaded, didn't consider dropping my payload. Does this sound feasible?

https://drive.google.com/file/d/0BxDe_g4a9D3PWHQ4Z2JGZ1lVTG8/view This one worked for me for Threat Guide4.pdf Actually, incase we lose that one, I've copied it to here: MadTommys_ThreatGuide4.pdf And an Excel file I put together using MadTommy's data and extra symbology. A10CThreatGuide.xlsx Always scan for virus/malware. This was safe when I uploaded it. But you don't know me, so don't trust me.

I've been hunting for info on how HOTAS buttons are setup in the actual jets. Accidentally found the company that manufactures the grips for our favourite vehicles. http://www.essexindustries.com/product-spotlight-showcases-wide-range-essex-platform-controls/ How sweet would it be if they put a little money into the gaming industry and made these things as USB devices?

Small strips of self adhesive velcro do the trick for me. 20mm by 8mm, in my case. I do get times where a piece blocks what I'm trying to read, but at least the whole panel is not blocking the view. I really wish DCS World had movable windows as I lose the bottom of many windows and have to close Ikarus cockpit. The right one is more stable but the left holds well enough with only the velcro on the side. Ignore that miscreant cable, it's tucked out of the way when in use. If anybody tries this, I suggest the hook goes to the screen and the softer loop side is stuck to the panels.

When I started reading this thread, I really wanted to play in this jet with this great Aussie camo that is similar to what I put on a model a few decades ago. Now, I don't want to play, I just want to see more of your astounding work. This is one of the best art galleries I've ever seen. (I'm 3 pints in, so that may contribute to my enthusiasm) Bonzer effort Strut. This is fantastic.

I have a close button at far top right of my Ikarus region, where it should be and another almost perfectly in the center. With the in-game cockpit behind it and it being along the top border of the lower screen, it's easy to not notice it until TrackIR picks up my head movement and this one little dot not moving is very noticeable compared to it's surrounding and breaks the immersion. It's the little things that ruin a marriage. ;) I can live with it, but I'm sure there's something I can do so I don't have to. Cover it with gaffer tape maybe. Gaffer tape fixes everything.... This was my first attempt with Ikarus. Not found anything yet, though I'm guessing there is a second panel somewhere that is creating this button. I am replacing the lower monitor this week so may be able to use the default Ikarus cockpit, or just recreate what I want from scratch for a better outcome than this first attempt.

Hardcore Coolhands. Looks fantastic. Does anyone know if there is a way to move or remove the 'X' close buttons that close the whole Ikarus panel down (image below)? I have 2 for some reason and one is in an annoying position. Perhaps there is another panel loading somehow that I have removed everything from. Either button exits the Ikarus cockpit. Opy

Came here looking for the same thing. Currently, I'm taking a photo of the message. Such a dicky method but I have no memory and it usually takes me a while to get to the right screen. Not sure if a mod could be implemented for recalling radio messages. I have a wireless k/b I could use as Galiptal has. Could look into that after I finish moving house. Love what CAT 101st has done there. I have my MFDs at the bottom of the screen and haven't setup Helios again since I moved last time. I've been looking into touch screen panels for 27 inch monitors. If I can sort that out, I may setup an onscreen UFC and/or CDU via Helios. Gotta be cheaper than the AU$1000+ plus postage from simparts. More for a CDU, but makes be dream of being rich. Perhaps I should stop simming and get a job. Pfft.