Leaderboard

Yesterday I spend my time for bits and pieces. After installing the new WH patch on gaming PC and server, I checked the latest behaviour of the JTACs. (Still the same but OK with the workarround). Then I checked the mission options, checked the payloads and skins, edited some briefings and started to create new briefing-pictures. I decided to release the BS2&WH missions first. Next week (maybe this weekend) I will release the missionpack. The BS2only missions will follow in the next version some day's after.

Not a problem. I just checked how much I've uploaded the full install...100GB. I thought 38GB was a lot. Looks like there is only three seeders for the full version.

I few weeks ago I stumbled on the "Inside view of TM HOTAS Warthog"-thread and read with interest about hairiness of balls and the stick's sticktion-stucktion-stickiness and different proposed solutions. Overall I've been quite happy with the stick, but being one of those claiming that the movement could be smoother I was not completely happy. In relation to that I readily admit that I might be quite picky about the smoothness. The stick provides good tactile feedback around the center, so I would rather avoid the proposed solution of removing the big spring and space-wise there is unfortunately no room for the garden hose neck extension. Instead I opted for the re-greasing solution proposed by Callsign.Vega. Below is a description of how I got the stick smooth using the Molykote EM-30L grease: Encouraged by Callsign.Vega's post and 59th_Bird's positive experiences. I moved on to contact Thrustmaster support to find out whether it would void warranty to open up and re-grease the stick. To my surprise this was not the case as long as the grease was intended for metal & plastic and I didn't break anything in the process: While it can become hairy to argue about the directness of consequences of action, I overall saw this as an encouragement. It's probably connected with the craving for disassembling and fiddling with all kinds of gizmos. I ordered the Molykote EM-30L on ebay. After receiving the grease I opened up the stick. While the initial parts opening the stick is well-documented by previous pictures and video, I have not found any guides detailing how the last part with the ball-joint is disassembled. Joe Keefe on simHQ mentions that he "... was unable to separate the two parts of the ball joint". Being careful and taking note of earlier mistakes involving the soldering iron [also see post 12 below], it took me some time to figure out how to disassemble the last axis. The procedure is to remove the two round parts that are visible on the plastic ball-joint: I used a 3mm Allen key to push them out from inside. It requires quite some force, so if attempting this please be careful. Here is a picture of the inner part of the ball joint with the two round parts pushed out from inside the joint (the metal visible is just part of the base, for fixating the ball when disassembling): And this is the inner part of the ball-joint (cleaned): Both of the two small plastic gizmo's have a small square on the upper side one should be aware of when assembling the joint again: After disassembly I cleaned all the grease of the plastic-parts with mild soap and water [also see post 9 below] - it took quite a while! Re-greasing them with the Molykote grease didn't take quite as long. When minding the wires as described in the thread about assembly everything slid into place! To my big surprise the new grease really has made a difference - smoother movement when starting and stopping motion are now much easier. The interesting part is how long this will last and whether the stick needs to be re-greased on a regular basis (hopefully this will not be the case). Happy flying!

Notice how the vehicles are easily spotted on the new TGP! Awesome! DCS A-10C Targeting Pod by __Wichid__, on Flickr

Einfach mal n bisschen online fliegen kann echt ganz schön kompliziert sein. Hier mal ne Liste meiner 1 stündigen bemühungen am heutigen abend online zu fliegen. -trackir an Target an Kopfhörer umgestellt Teamspeak an neue IP rausgesucht -Auf 104th Server mit KA50 gegangen -Keine ka 50 plätze -> auf A10 gewechselt -Wartezeit -> Score too low raus geflogen -Anderen Server probiert kurz nach cockpit abgestürzt-> zu ka 50 gewechselt -Trackir nich erkannt (blaues licht fehlt) -> game wieder zu -Internetverbindung weg 10 min warten -Mit KA50 auf Server gejoined Farp war zu weit vom einsatzgebiet weg ich solle auf A10c umsteigen -Auf A10c umgestiegen server gejoined -Gestartet, Karte war langweilig (wahrscheinlich Übungskarte) 2 panzer gekilled sinnlos rumgemehrt -> Kompressorstall -Vergessen wies geht -> Notlandung -Server verlassen. -Keine Lust mehr Forenbeitrag verfasst und Joystick mal wieder in die Ecke gestellt. :joystick: Geht mir hin und wieder so von diversen zufällig auftretenden Soft und hardwareproblemen mal ganz zu schweigen. Manchmal machts echt überhaupt kein Spass. Komischerweise sitzt man dann n Tag später trotzdem wieder dran und wenn man es nicht erwartet bekommt man beim ersten Server den geilsten Flight ever serviert.

Когда я служил в советской армии, то нам выдавали в караул 60 боевых патронов, которые мы тут же заряжали в два по 30 в каждый рожок. И никакого врожденного дефекта я не наблюдал. Бред какой-то несешь. То что у вас в части отцы-командиры наверно продали весь боезапас бандитам и терорристам, то тогда согласен. Думаю ты так служил, как я был на луне. Так что святое не трожь.

BINGO OK Did yet another download on the exe file but this time took it from a German site, and hey its' working. Very strange how the USA one's were causing the problems. So to everyone here at DCS I thank you for all you help, and would like to remove my refund request for with. Timm

THE best ! :thumbup:

Had the same problem here is your answer :) LINK

PM i am sure for some decent help, people here will need more than just "it crashed, what happened"? crash logs, tracks etc, would help everyone. not trying to sound condescending, but DCS needs more info.

You only have to go back 1 page for your answer.....hell its only 3 posts before yours....LOL ;) LINK

In my experience it varies between aircraft types, the obvious reason it that different airframes have different radio configurations. Most fighters, for example, only have two. In the harrier for example they say push left or right. On Typhoon it's just push one or two, because both radios are UHF, VHF/AM and FM combined systems and are all controlled digitally. For the Hog FWD, MID, AFT makes perfect sense, and as Paul says is how it's done IRL. Also from what I've been told by the pilots I've quizzed, it's pretty much unheard of for pilots to actually announce a fequency over comms (ie "push 150 V) when in combat. Much like the way radios are used on the ground, aircrew will have lists/tables of frequncies relevant to their mission/area of operations and code names are used for specific frequencies, in additon to pre-sets for common frequencies. For example, AWACS might instruct a flight to contact a JTAC on "TAC 36". TAC 36 would be the code for a specific radio frequency listed in their kneeboard tables. By doing this, nobody who shouldn't know can follow a flight around the radio network over unsecure comms, and it's also easier to remember a code word spoken over the radio while doing other things than a series of numbers. As for TARS and having the option to chose which radio runs over which sound channel, imho even if the Hog doesn't work that way it's a great function to have. Just beause it's not 100% accurate doesn't mean it's not a good idea, they just never got round to adding the function to the Hog.

:smilewink: I really have to do some kind of things like that to "sleek the waves". But not till next week... this week is EDITORTIME! :joystick: Edit: and if you really want to donate... PayPal is my friend. ;) admin@spare-time-pilots.de

Yeah, between the time taken up with RTS's and porn theres not enough time, or energy for much else. :joystick:

I agree, the pyrotechnics is the only area that's wanting. Especially when so much time is spent peering at grainy black & white camera feeds, it'd be nice to see some more dynamism in the kinds of things that happen on there - Even in the old Gulf War LGB clips you get all sorts of burn-in and "ripped from the headlines"-feeling streaks and other artifacts. A few years ago there was a Red Dawn-inspired strategy game called "World in Conflict" that had a look that was a nicely done blend of realism and showmanship. The explosions were colossal fountains of dirt and didn't feel too "Hollywood", but were still made with an artists' eye and actually reminded me of the more photogenic examples you might see in a military documentary, and despite their shimmering 3D shockwaves and arcing tendrils of debris, they seemed to go very easy on system resources. I have no idea how they were implemented, but I'm sure someone here would be able to tell at a glance. Since so much of air combat takes place at ranges where there isn't a lot to see, and simulations are a primarily visual medium, I don't think emphasizing the action you actually can see is out of the question, especially if - like a backstory between missions - it helps you feel just a little bit less like you're actually safe at home, staring at a glowing rectangle. I can understand why it's been put on the backburner since it is more "game"-y than things like the environment, let alone the aircraft itself, but what better reinforcement for successfully learning the sim than being able to make a big, crunchy explosion you can almost feel the heat from just by looking at it?

See the picture in the first posting. The arrow shows (almost) the same direction like the runway (right-to-left). This means that this runway points to the north.

thios is going to be sooo good when you finish it i would'nt be suprised if you got offers from some pit building company or rich man to build him a pit. this is possibly the best thing i have ever seen around the net mate. I want to cry just looking at it. truly your are an insperation. Me and Dolimo are thinking of bulding a sim pit together. all the best of luck buddy

Ok just found another item not working...the RWR. To get it exported you have to do it the same way that HellfrogC6 explained in the blackshark2 thread. All credit for this goes to him as I just copied what he did in the BS2 over to A10 and it worked...so here we go: Open up file x:\Program Files\Eagle Dynamics\DCS A-10C\Scripts\Aircrafts\A-10C\Cockpit\AN_ALR69V\indicator\AN_ALR69V.lua Add the lines highlighted in red below. The line that has the RWR_SCREEN in quotes is what you put into your monitorsetup .lua. It can actually be named anything provided it is the same in your monitorsetup .lua dofile(LockOn_Options.common_script_path.."devices_defs.lua") [color=red]dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")[/color] indicator_type = indicator_types.COMMON [color=red]purposes = {render_purpose.GENERAL}[/color] [color=red]try_find_assigned_viewport("RWR_SCREEN")[/color] ---------------------- 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" } My monitorsetup Lua _ = function(p) return p; end; name = _('Airdogs Pit'); Description = 'Indicators configured with Easy Monitor Setup' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.77777777777778; } } RIGHT_MFCD = { x = 1890; y = 1143; width = 860; height = 430; } LEFT_MFCD = { x = -830; y = 1143; width = 860; height = 430; } UHF_REPEATER = { x = 415; y = 1782; width = 140; height = 20; } DIGIT_CLOCK = { x = 113; y = 1891; width = 200; height = 100; } RWR_SCREEN = { x = 252; y = 1354; width = 300; height = 150; } CMSP = { x = 1775; y = 1637; width = 600; height = 75; } CMSC = { x = 752; y = 1379; width = 420; height = 65; } UIMainView = Viewports.Center

Wow, I just checked how much I've uploaded the patch on bitorrent - 38GB thus far. Waaay more than I expected. Guess there are a lot of people who want this patch :) The faster everybody gets it, the faster we get more people back in multiplayer.

I wrote an update about the upcoming patch on the TARS site. It won't be long now--hopefully this weekend!

Well howdy shoot! You boys can keep your 1.1.1.0 patch and it's new bug(s). :cry: A long time ago in a land, far, far away, software developers actually beta tested their software before release so that things like this wouldn't happen when the end-user installed on their computer. I mean, the idea of patching software is to generally improve it, not render it something less useful. Oh well, thanks DCS for wasting my time downloading and installing the patch, along with having to reinstall 1.09 now. Yippee. :pilotfly:

I got a similar problem like EagleEye. I started the campaign shortly after the release of the first patch and I really enjoyed it. TKOH is the game I waited for since SimCopter (:D) and they did almost everthing to make it a pleasure but the FM which is tuned in the next patch can be a real show stopper. I crashed 3 times yesterday where I simply had to land on a field and I crashed three times. Fortunately it saves quite often. Remark: I successfully landed many times before + several sling load missions including rescues from a ship. In some cases the FM is just not controllable. They just need to get out this agrressive rolling tendency and the collective needs to be tuned as well so you can descend more effectively. I see all of that under the game tag and it seriously won´t harm TKOH if those things get sorted out in the next patch. It doesn´t has to be super real but at least it should be contrallable similar to a real chopper. Looking forward to the patch.

Yes seems we have entered a new cycle for flight simming... The only drawback is: They are much more comlete in the sim department than in the golden age so now it takes a lot more time to be proeficient with them... There s really not enought hours in a day. Nor enought memory in a head...lol You start getting on one and start loosing skill on the other!!! RoF CloD K-50 A-10c TOH And add some space sim and BMS and its total madness.

Had some nice cushions made for my pit :thumbup: