mjolner

Most of the skins are located in Bazaar/world/textures. You will need a cdds viewer/converter to change the file to bmp that can be manipulated using Psp or similar program. Again can't recommend lockonfiles enough. There is an excellent Pdf tutorial for BS. The file scheme has changed slightly for BS v2. Flanker explains all this in the above link.

Additionally under the descriptions.lua (open with notepad), you will see the country name, for example, "RUS" for Russia. You can add the "country code" to any of the skins you want and they will all be accessible in the mission editor for which ever country you desire. If you add completely new skins keep in mind that they require entries in the graphics.cfg file. I am at work so I cannot give more specific example. Recommend lockonfiles.com for more info.

I am not sure of exact numbers but I would say the A10c collectively inside and out has a much higher polygon count, speaking from a purely visual based opinion. I am getting around 20 FPS less in BS2 than A-10C. I have played around with the various settings and have matched the display options for both sims yet cannot get BS2 to run as fast as A-10C. While I am not overly concerned, maybe a patch will smooth things out? In any case, the Alt-tab situation definitely deserves EDs attention.

Press R ALT + ENTER to bring up the axis indicator, you can use it to see exactly where your trim is set. Crosswind can also be a factor. Practice acheiving a stable hover without pressing the hover button.

If you have DCS A10C the GUI manual goes pretty indepth with most of the functionality of the editor. Same for BS 2 if you have already purchased. As far as randomization, do you mean random missions or random events occuring within a created mission? BS2 comes with a mission generator that works just great for setting up simple missions with random units and various random parameters. With the editor itself, I am pretty sure you can set triggers to spawn random units pretty easily, I have never used it myself. You could probably set just about any varible you desire with triggers.

Thats pretty slick. I wonder how accurate the coverage area is.

Arran Try using Active-pause for practice sessions. Set up a mission with both static and moving armor and trucks, etc. Keep them within a close radius say less than 10 miles or so and set the targets within that radius at various distances and mix up the terrain a bit as well, trees, open fields and suburbs. Fly to a set waypoint near your targets within 10 miles, hit active-pause and start hunting. Active pause lets you interact with the cockpit while your hog is completely stationary, your moving targets continue to move, etc. You can play with SPI, SOI, and TGP till your palms grow hair.

I may have missed it if someone mentioned it already, Right ALT+ ENTER brings up the axis-indicator thingy, this is very handy for getting a visual on where your trim is set if you are not using an FFB stick or are having other technical difficulties. On a different note, some say not to use the trim reset button, I use it when I need to center my trim when I am getting ready to hover, time now, once you learn to control your ship, you may find it a useful button too.

Page 508 in the manual: RED station. A red station generally indicates a profile and inventory conflict. This will happen if a loaded weapon profile includes a weapon that is not loaded on the aircraft. This can be remedied by using DSMS Inventory to set the correct store or clear the station showing the error. If the hard points in question are of the same type this should explain atleast part of the problem. Red can also mean a hung store.

In the radio comms section of the manual, page 644, there is a great description of the 9 line as it works in game. Might not be perfect but from a mission building perspective it works rather well. Make a simple mission,place some targets, drop a predator in, assign it as a JFAC and go. I like the fact that I can set the JFAC to identify targets however I like, coordinates, willy pete, whatever.

Hey Rocky49, I initially did not understand JTAC procedures, but figured it out. At first it seems more complex than it really is. The manual is actually pretty clear on the flow of events and the built-in radio comms sequence pretty much does the leg work for you. Maybe try posting some specific questions about what you do not grasp?

Active Pause is great, I definitely abuse it, I reassigned it to the P key, probably should'nt have because now its too easy to use. I wish DCS:BS had that one.

Not meaning to sound like an obtuse prick or anything but the tutorial missions are actually quite useful in explaining basic weapon deployment as are the numerous video tutorials on youtube. Just a friendly recommendation. You won't get too far without some understanding of SOI and SPI.

Check your IFCC switch or bar that go through the startup tut.

Amazon.com and Tigerdirect.com are also good bets. If you live near a Fry's electronics they carry it in stock. They only carry a few at a time but lets face it, it is a low demand item.

When you run the script in TARGET do you get the green text similar to this? : *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll" Physical USB HID devices managed by script! Currently plugged USB HID devices[3]: 1: "HOTAS Cougar Joystick" - "USB\VID_044F&PID_0400&REV_0110&MI_00" 2: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 3: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100" USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\5&20A9C10C&0&1) selected USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\5&21C22887&0&2) selected USB HID device with hardware id "VID_044F&PID_b351" cannot be found USB HID device with hardware id "VID_044F&PID_b352" cannot be found Virtual HID devices managed by script! Connecting virtual joystick...Done Device name set to Thrustmaster Combined Connecting virtual keyboard...Done Connecting virtual mouse...Done main returned 0 ( on my setup the cougar is listed because I still use older rudder pedals via the cougar base, so yours might not list that. ) And when you run the device analyzer ( with script running ) do you get normal responses from all your buttons and axis? If yes to these then TARGET is working, if no try reinstalling TARGET and be sure you are running RC3. These seem obvious probably but i had to cover them. When you run a profile just the throttle is dead and not the stick? If that is the case you might try a reset of the throttle flash rom. I know the procedure is listed in the threads about "dead throttles". Bar any of that I am baffled. Wish you were running WIN 7. I would honestly attribute this to TARGET being such a new app, you may have to go without until TM gets things polished.

Jcook Which function are you specifically having issue with and does it work outside of the tutorial mission? Are you panning the view in the cockpit in the direction of the arrows? Hit ALT+c to turn off the yellow cursor, pan and hit ALT+c again. Try that.

Thanks Ice and Evil, this was a matter of not following directions on my part. After given the vector by ATC and autopilot disengage, I was changing course to the airfield steerpoint and not the vectored course from ATC, this put me directly over the airfield and not 10nm off the runnway as needed to capture the glideslope. All is corrected now and I have completed the tutorial, a very well made one at that. Very informative. I was landing fine before but my airspeed was much higher than the prescribed 120 for a light bird.

Thanks Ice I will go and try the training mission again. I recall there is a point when you are directed to contact the tower or approach by ATC, I think when you are in visual, but I was waiting for a prompt from the tutorial voiceover, maybe this is where I am screwing up. I will give it another try at first opportunity.

I cannot seem to get this one to work, but I am not sure if it is an error on my part. Initially your waypoint(steerpoint) is about 10 nm off the runnway at Batumi. Once the tutorial starts you are directed to bring up the CDU and divert to Batumi. This new steerpoint takes you directly over the airfield? Is this right or am I flying to the wrong point? Its hard to capture the ILS over the airfield. Once I fly over the airfield the voiceover never picks up again. Can anyone help me out with this or provide a track of the completed tutorial?

Yes TrackIR5 will work with the A-10C however only in 32 bit. You must load the 32bit files when you install the beta and then run the DCS A10C_x86.exe. Also if using win vista or 7 you need to run both trackir and DCS as admin. Currently there is no 64bit support for the beta, coming soon, so I hear.

I believe the term is " Fratricide ". I hate to be the spelling nazi but I just could'nt resist.

Just for further data. I too am experiencing this crash, only in the A10 and only when switching weapons with the D key. I am using a cougar. Not using profile, just mapping keys direct to the stick. My system specs: WIN7 64 I7 920 @ 4ghz, running default speed had no effect. X58 w/ latest bios 6 G DDR3 1600 RAD 5870 with cat 10.2 SB Xfi xteme gamer Also, fault only occurs in fullscreen mode.

One possible solution for you. Try amazon, search for "the ultimate fighter collection" UBISOFT. Usually runs about $10.99 and you can get free or cheap fast shipping. Its a 3 CDROM set containing, IL2, Pacific Fighters, and Lockon. Its not lockon gold, its the original game, will need to be updated with FC 1.12B or something. You will still need to purchase and D/L FC. You probably would want to pay more for the speed of a download version but since none exists and you will have to wait anyway, why not save some coin.

Been an OFP, ARMA, ARMA2 player for awhile. I built my new system specifically for ARMA2. I am fairly certain any rig that gets 80 FPS in ARMA2 will run DCS very well. The Armaholic site has a nice benchmarking program for ARMA2, the name escapes me at the moment. I would be curious to see what your numbers would be like if your claim of 80 FPS holds any merit. Not saying its not possible but I would feel more comfortable knowing your rig. ARMA 2 and FSX are far more demanding on processor cycles than DCS. Hopefully on this forum you find some answers to solve your performance issues.