Leaderboard

*UPDATED TO V1.7!* Another mod put together for your enjoyment, this time i've hunted around and pieced together a single .cdds skinpack for a bunch of some of the ugliest looking stock model jets/objects in lockon :D ******IMPORTANT! : PLEASE UNINSTALL PREVIOUS VERSIONS IF YOU'RE UPDATING TO A NEWER VERSION, OR SOME TEXTURES MAY NOT SHOW!******* Some details: 2048x2048 resolution C-17A Skin by iViper MiG-31 "Tambovskiy Wolf" 2048x2048 resolution 1024x1024 resolution detailed R-27 missile skins 10x F-14 Tomcat skins in 2048x2048 by Alexandra E-2 Hawkeye 2048x2048 resolution skin 2048x2048 resolution KC-10 Skin by Flanker 6x Mirage2000 skins in 2048x2048 resolution 3x Su-17 Skins in 2048x2048 resolution by Flanker Tu-95MS and Tu-142 skins in 2048x512 by kyborg Admiral Kuznetsov repaint by 159th_Blackhawk 2048x2048 resolution Tu-160 skin Engels AB Ticonderoga and Oliver Perry repaints F-16CG-CJ War Pack Textures by D-Scythe 2048x2048 resolution C-130 skins by Alexandra High resolotion An-26 Aeroflot skin High resolution detailed civilian vehicles skins High resolution camo skin for ATZ-60 fuel tanker Luftwaffe and TuAF F-4E Skins IAF F-16C 2048x2048 resolution Skin TuAF F-16C 2048x2048 resolution skin by 141st_c@sper Tu-22M3 Cockpit glass fix and improved skin by Jetfire Removed S-3B "Shamrocks" skin from previous versions and replaced with different skin Included improved Luftwaffe numbers and badge markings USS Carl Vinson "Dirty Decks" textures by iVIPER21 (appologies if i've missed any artists out!) VERSION 1.7 AVAILABLE HERE (MODMAN compatible) http://files.lockon.ru/en/111/

Version 1.6 of my ME mod is available. Originally created for DCS it should also work with FC2. Please use the original thread under "Announcements and Updates" to post problems and suggestions. Thanks. The MOD includes the following features/ changes: General You now can change coalitions at any time (by clicking the more or less new button in the toolbar) :) At least a small portion of the unit-duplicate button is visible for users with horizontal screen resolution of 1280 pix Trigger Editor Newly created trigger objects will be inserted into the trigger list behind the currently selected trigger item - not at the end anymore. The added buttons "+" and "-" move the currently selected trigger item one position up ("-") or down ("+") within the trigger list. Element positions are persisted during save/load cycles. The new button "DUPLICATE" creates a deep copy of the currently selected trigger and inserts it behind the selected element. (requires a screen width of more than 1280 pixels to see all buttons) Changed the width of the two trigger edits "Name" and "Type" to enhance readability. If this proves to be helpful other edit box widths could be changed as well in future releases Unit List The new button "DUPLICATE" creates a deep copy of the currently selected unit group including waypoints, targets, target categories, units and their payloads. The new buttons "SHOW ALL", "HIDE ALL" and "TOGGLE" work like their counterparts in the trigger list dialog. Only the visible list elements are affected. So, using the filters, you can selectively show or hide groups of elements or toggle between them. [Rem: The button "Duplicate"is not localizable, what means, it is in English always.]

A bunch of photos I took on the Dutch "Open Dagen" this weekend. Taken with a Nikon D300 + 80-200mm f/2.8 (not quite enough zoom for airshows though).

Poor ref is going to cry at home when he see the replays. Kaká didn't deserve that at all. If anyone should get a card, it is the Cd'I player, but he's not the only one... They went kung-fu style, all-out, kill 'em all. Tioté scored a very violent hit on Elano and didn't even get a f***ing yellow card. That foul would've bought him a red in a normal situation, but that wasn't the case. At least, at first sight, Elano seems to be OK. A few minutes later and the same thing happens again, now with Michel Bastos. The ref' gives the guy just a yellow... Then the ridiculous series of fouls and free violence evolves into that shameful incident with Kaká - not to mention his first card wasn't exactly a good call. What a stupid decision... I hope FIFA hasn't lost sanity and will remove this card. As a note, Luis Fabiano's [classy] goal had two hand-balls as well, but our blind friend once again missed it. It happens, of course, but it shouldn't, not with such rate. I hope it was just a [very, very] bad day for the referee and he'll go back to reason in the next games, but that probably won't be forgotten... Well, we're through, Elano's condition isn't too bad, Kaká went off with his dignity untouched. I hope against Portugal we'll start seeing some Fair Play again. Can't wait for that game :) Good luck against NK

You can forget it in a fully loaded flanker. Once your fuel is down to some 60%, you might be able to stay up there in MIL.

Use a zoom climb where before you climb, you build up great speed in level flight or a slight descent up to almost you max speed, then climb at a shallow angle, say 10 degrees to 12K M. Once up there no max G turns. Go easy on the stick.

It's pretty high if you ask me so in case on lots of payload and fuel onboard AB is a must for flying level and maintaining speed. "Flaps" light do not necessarily indicate Flaps, you're flying high AoA here and slats on the leading egde of your wings are automatically deployed.

yes i know but you can see where those 2 tomcats where and I couldn't get them to show up all the way to them.

Wicked pictures Frazer! :thumbup:

There's a new feature in FC2 that automatically detects how much of the included PDF-manual you've read. If it sees that you've read the chapter about A-A-radar usage, it will automatically patch up the game for you, and then the radar should work as advertised.:thumbup: There is a cheat for it, if you don't want to read the manual but still have the radar work properly : go to your install-folder, and look for a file called rtfm.exe in the temp-folder. Double-click on it, and it should work. I'm just screwing with you mate. The bug you're experiencing can't be fixed by a patch unfortunately, since you are the bug. Learn how to operate the radar properly by reading the manual, searching these fine forums and asking questions here. If you can't see airborne targets 20 miles in front of you, your either pointing your radar-cone over or under the aircraft, or they are beaming you and therefore your radar can not see them.

Yea the blue F16 is the Belgium Solo Display Team, great skin, great demo (though not as good as the Dutch F16 solo display team obviously) :D

Which stick are you using? Generally, I assign through going into Options > select an aircraft > Axis Commands > select throttle and select assign, then I move the slider/throttle I want to use. Note that you want to be sure you are assigning for the aircraft and game mode you are using since each aircraft has their own assignment.

It truly is sweet...when it all works! The usb screens I'm using are the Mimo 7" mini monitors ( http://www.mimomonitors.com/ ). They are quite neat and come on their own twist stand ( portrait/landscape), they have just the one output, a twin usb lead ( though it seems to work well just using the one usb ). The MFD's are from Thrustmaster and again are just plug and play with a usb lead. The MFD's dont fit exactly onto the monitors, but a little black insulating tape soon covers up the overlap! To program the MFD's while using LEAVU over a lan I used the freeware "Xpadder" ( thanks to Schizwiz for pointing me in the right direction )which was actually pretty straight forward after my initial minutes of staring blankly at the screen thinking "what the f...... do i do now" - If you take a look at the LEAVU thread ( http://forums.eagle.ru/showthread.php?t=53464 ) it shows some differant kit running it all.

I don't recall what you refer to as "things went to ****" (unless you refer to the very old coroutine based implementation), but that is not really relevant is it? What is relevant is: 1. For the next event I recommend the following: Make a pack, a locerf-pack for modman, where everyone gets the standard files. Everyone needs to be integrity checked, not for this or that mod, but to ensure everyone has the same flight models, weapon data etc, so that game does not desync and crash. 2. The server MUST run a stock setup. Zero mods or changes, nada, zip, null. 3. If you are going to host ATC, let a secondary host run it. do NOT risk the game host. LRM was server side. Eri and Leavu are exclusively client side. They cannot affect the server. Furthermore the (once again purely CLIENT SIDE) exports of eri and leavu have far less cpu requirements than lrm ever had. Calling local client exports the culprit is just as intelligent as saying "oh my mouse driver is wrong so that crashed the game server"... or "my joystick has macros so that eats more CPU cycles and crashes the server machine" Furthermore both leavu and ERI have (unlike lrm) already been tested by a huge number of people, and, it is built on the lessons learned from lrm. One serious point people seem to be missing is that _you cannot disable export.lua from running: - You can make them standard (not send data to external apps etc) but the export.lua is always running. It always runs "LuaExportBeforeNextFrame" functions etc, whether you like it or not, or whether you set anything to false or not, the variables are already exposed whether you intend to use them or not. BUT!! There is one possible crash issue with exports, but naturally this has to do with GLOBAL exports on SERVER. Unlike Fc1, Fc2's function "LoGetWorldObjects" exports everything from aircraft down to every single bullet. The sheer cpu/memory load of exporting all that data does take a LOT of fps, so that is why I really recommend that the game server absolutely must run standard/stock/unmodded settings for large events. The game is a 32bit app and has issues with running out of memory space since no cleanup is implemented (if it loaded one AC once, it stays loaded), as discussed in other threads and confirmed by c0ff: Therefor server must not run anything that increases memory usage. Stock setup, low gfx only! In general people need to stop jumping to quick conclusions and instead start thinking logically, actually trying to work out why something causes a crash. People need to stop using crash events like this as an excuse to bash other software that has absolutely nothing to do with it. It will only accomplish 2 things: 1. Not get the crashes fixed 2. Create personal conflicts. Do you want a long term deterministic solution or a "quick fix" that only out of sheer luck and coincidence happens to work (due to magic of probability/statistics) the next time?

here it is F/A-18 part at 2:10

Great Vids guys this is how the Mig-29K looks In Indian Navy. These Pics are from a couple of weeks back IAF Su-30MKI Flag off..leaving for Indo-French Garuda Air Exercise at Istres Air Force Base France.

you might also want to take a look at the producers note #8 video, that explains the datalink panel pretty well: http://www.digitalcombatsimulator.com/index.php?end_pos=133&scr=products&lang=en I'd suggest watching the other producers note videos too, aswell as watching the ingame "Tutorial" missions. All important systems are explained there.

Thanks much for the putting together part Appreciated

Uploaded with ImageShack.us

Очевидным является патч по исправлению ошибок, а не совместимости с А-10С, так как новый сим выйдет ещё не известно когда. Так о какой совместимости может идти речь?

It already runs over network, you can hook up multiple units to the same game computer. To be able to run it on Ipad I guess we would need to remove the JOGL parts of it. (unless JOGL works on ipad?) Do you know if Java has good native graphics capability for rendering primitive shapes fast? - Basically to do this I would need to be able to draw lines, triangles and text, but that is basically everything I need.

Нет травы - "Сделайте нам красиво!" Есть трава - "Смерть ФПСам!" Уж разберитесь? :huh: