Druid_

The ME brief is lacking in the amount of detail a mission builder can provide. Its possible however for mission builders to provide a mission with all of the necessary intel, you just need to include the mission and the briefs in a zip file. The brief should ideally include a .pdf with all of the mission info including intel pictures and maps etc. I have something I am pulling together and will post it up soon. It will include; Satellite pics of target area, Route map, attack run(s) maps and a knee board quickglance mission brief as well as the brief from the DCS Mission screen.

A divorce settlement where she gets everything?

Not sure about solid source but ... http://www.pureoverclock.com/review.php?id=1185&page=10 Quote "We've been told that the D1 stepping is pre-production, while retail chips will come with the D2 Stepping."

Some important info from overclockers.co.uk on overclocking sandy bridge :- Core Voltage - Not recommended too exceed 1.38v, doing so could kill the CPU, we therefor recommend a range of 1.325-1.350v if overclocking. Memory Voltage - Intel recommend 1.50v plus/minus 5% which means upto 1.58v is the safe recommended limit. In our testing we have found 1.65v has caused no issues. BCLK Base Clock - This is strictly a NO, anyone using base clock overclocking could/will cause damange to CPU/Mainboard. (Set manually to 100) PLL Voltage - Do not exceed 1.9v!! Processor - Basically we recommend customers not to exceed 1.35v to play it safe, all our bundles are set at 1.3250v or lower, any competitors offering bundles above 4.6GHz you should be enquiring as to what voltage they are using as we believe anything over 1.38v will limit CPU lifespan and anything over 1.42v will likely kill the CPU or severely limit its lifespan. Memory - Intel recommend 1.50v plus/minus 5% which means 1.60v is the ideal safe maximum, but we have found in our testing all 1.65v memory is fine. We have also found most new 1.65v like Corsair XMS3 will run at its rated timings with just 1.50-1.55v which is well within Intel specifications. So people upgrading to Sandybridge you can still use your old DDR3, but we do recommend you run it at 1.60v or less. We are shipping most of our bundles which feature Corsair XMS at 1.50v-1.55v at rated timings. We've also discussed with Asus and MSI regarding voltages for memory and they also confirm in their testing 1.65v caused no issues with reliability. Base Clock - To put it simple if you value the life of your components, do not overclock using base clock! PLL Voltage - Again do not exceed 1.9v! Full article here

Didnt say they would be. Having 'not' said that however, it should make things easier.

So none of the BS code is portable or applicable to the ah64? I thought maybe blade aerodynamics had been modelled and would therefore apply to any heli with tweaking of course?

Hmmn, let me see, DCS a ground attack series so far, helicopter aerodynamics already coded and rely on contract work for the military. My money lies on the Apache ah64. I would also be surprised if at least some of the team weren't working on it now.

Like what you're doing here. When it comes to populating buildings and vegetation, I'm not sure if it possible to import objects from google sketchup http://sketchup.google.com/ but if you can it will save a lot of time. There is a massive community of buildings and vegetation in there. Someone has already modelled some of San Francisco here. THe golden gate bridge here. You may have to modify a lot of it to keep the poly count down but its a starting point.

Depends on wether you are setting QFE or QNH. QFE sets altimeter to read zero at the runway in use threshold, QNH is altitude above mean sea level. A lot of military SOPs set QFE for take-off and landing. They then either use a regional pressure setting, QNH or 1013 (Standard).

From what I read it might be more of a current software issue than a hardware one. I'm sure the clever boffins will come up with a solution. "Quick Sync—a blanket marketing name for Sandy Bridge’s ability to accelerate decoding and encoding/transcoding."

Looking at the multiple performance tests run on a normal and overclocked 2600K at http://www.pureoverclock.com/review.php?id=1178&page=1 I think that you can expect modest increases in FPS from a 3.9Ghz i7-930 if you put in a 2600K. If I had to put a figure on it, based on the benchies so far, I would say 30% increase wouldn't be far off. Worth it? for me, hell yehh. But then I do use my PC for Video/photo editing etc ... nah fk it, I'm a speed freak (once an overclocker, always an overclocker). I'll let you know for sure as soon as I can get my hands on a D1 stepping 2600K.

Hey Bahger, I warned you that mission building in beta stage would be a frustrating experience. There are guys getting crashes in the ED missions so I don't think there's necessarily a bug in yours. Its a GUI mission builder so you shouldn't be able to crash it in theory. My only advise would be to send ED your crash file and let them pick through it. Given the ED testers/developers involvement in other Forum sections, I find it a little disheartening to see very little from them in the mission editor section. Bit worrying really.

Set up the AXIS for your joystick in pitch and roll with curves that allow it to be less sensitive near the neutral point. Then .. 1) Formate on the tanker to one side. Once you have nailed his speed - TRIM 2) Once you have done your checks, ready pre-contact 3) Move smoothly behind tanker 4) Put HUD pipper just above boom wings on boom. 5) Move in slowly, at 10ft from boom, hold position and get stable, retrim if req'd (you shouldnt have to if you got 1) right). 6) At about 6ft boom operator wakes up and boom raises into position, ease forward at less than walking speed. 7] Try NOT to LOOK at boom initially, follow centre line of tanker 8.)Move in slowly, boom operator will guide in and .... 9) 'contact' your taking fuel. 10) try and keep boom 'green' section exposed. Amber = do something, red = bad. 11) Look at tanker and not at Boom i.e. you are formating on tanker not on boom. 12) Main problems ppl have is approaching too fast onto boom, formating too high or too low. 13) If you need to reconnect to boom then PRESS the Nosewheel Steering button (this resets the refuel process). Don't be to aggressive on the throttles, I think the correct word here is ANTICIPATE. I use a max of 4% fan speed throttle changes You cant use the Autopilot with the refueling door open (its disconnects the EAC). So nail that trim and practice practice. Were the tankers set up on different frequencies?

Now stop slacking and get to work on the TMS map !!

I think its great as it is without the TMS. otherwise it would get cluttered as you have mentioned and therefore more difficult to reference quickly. A completely seperate diagram for TMS would be my preference. Also, 1 other small request. Can you do a printer friendly version (the backgrounds are great but eat up ink).

Crikey, that was quick. Perfect !

Nice. I would add that with HUD as SOI, DMS up/down can also be used to cycle Mark Points and not just Steerpoints (when MARK is selected). So maybe change it to Steerpt+/Mkpt+ ?

Understand, but for those who want multi monitor support the AMD is probably the way to go.

or get yourself a AMD HD6950 and turn it into a HD6970 for free http://www.techpowerup.com/articles/overclocking/vidcard/159

Great, ok now try upping the voltage on your CPU from 1.2v to 1.3v and start increasing your BKCLK in small increments. Hopefully, you'll reach 200. This will also increase your memory to 1200 Mhz which it should manage easily.

A lot of enthusiasts are able to reach 4ghz on a D0 stepping I7-920 with a Vcore of around 1.275v When overclocking, start by underclocking your memory (use a high ratio to do so) so at least you will know its the CPU causing problems and not your memory. A simple and quick guide (please search web for more in depth versions) 1) Set your multiplier to 20, your Bclk to 200 Mhz. 2) Disable Intel Turbo boost and any other power saving options (e.g. EIST, C1) 3) Drop your memory ratio to 6x (it will run at 1200 Mhz, you can tweak it higher later) 4) Set Uncore frequency to run at 2 x your DDR3 set memory speed (in this case 1200 Mhz) so in this case 2.4 Ghz (in some BIOS it might be a multiplier, in which case set it to 12 (i.e. 12 x 200 Mhz) or even slightly higher but not lower. 5) Set QPI/VTT to 1.5v and QPI PLL at default 6) Set CPU Vcore to 1.3V If you have OC probs then you can raise the CPU Vcore to 1.4V but do so in small increments. Use the freeware 'CPUID Hardware monitor' to check your BIOS voltages are close to those set in your BIOS. Once you have a stable CPU overclock, you can start playing with your memory speed and timings to increase performance further. Good luck.

Hey Mower, what stepping is your i7 ? looks like it might be a C0 stepping version. If you have a Gigabyte mobo, this an excellent link (prob good info in there for other mobo users also) http://www.overclock.net/intel-motherboards/706509-official-gigabyte-ga-x58a-ud3r-ud5.html Most i7-920 D0 stepping enthusiasts manage 4.0 Ghz on good air cooling

Personally, I'd wait and see what Beta 4 has to offer. Hopefully, switch waypoint and orbit in the ME will be fixed. Also maybe tanker will allow more than 1 go at refuelling.

Ho Ho Ho Well, Blindspot was responsible for the last badly needed update to the ME (AND / OR). Satellite view was at the top of the list after the release of BS and its still at the top of the list apparently. Opening 2 instances of the Sim, sp & mp and saving, alt-tabbing etc etc is really something I was rather hoping they would address. If you do a search on the BS forum you can see how much of an issue it was to mission builders. It increases build times by a factor of 3 at least. Anyway, nuff said, I've flogged this dead horse before.

It will be fixed in final release, at least I hope so. Having said that, there's little or no confirmation of Mission Editor bugs or problems from ED so we will have to wait and see. Historically the ME has received little attention (e.g. Still waiting for satellite view), this version if they get it working 100% with current features should be much better. Still need satellite view though. Time will tell. p.s. Did I mention it needs a satellite view for placing units?