Cionara

I post here, too so maybe I can find help. Or you can test if you also got the bugs. Someone else getting the problem that you can't turn on cockpit lights (k) when starting on a FARP at night ? This problems stays even when flying away. Runway is ok. When I remove d3d9 file in Bin\Stable all lights and stuff is working fine. Somebody has an answer why starting from a farp makes it that buggy ? Also no reflections at night at all. KA 50 stays dark when dispensing flares.

I love this mod, it makes the sim looking very nice but... Someone else getting the problem that you can't turn on cockpit lights (k) when starting on a FARP at night ? Also there are no reflections of flares and stuff when starting from a FARP and this problems stays even when flying away. Runway is ok. When I remove d3d9 file in Bin\Stable all lights and stuff is working fine. Somebody has an answer why starting from a farp makes it that buggy ? Also no reflections at all at night. KA 50 stays dark when dispensing flares.

Yes they are. But I keep wondering why cockpit lights work on runway and not on farp =( Also strange that the bug keeps on even if I fly away from that farp. You could be right that it's an shadow issue. But tested with shadows on "high" and didn't get better. All light sources are bright but nothing gets enlightened by it when starting from FARP. Edit: I tried a bunch of things out and when I remove the ENB Series d3d9 file problem goes away. But I want to keep that HDR mod. And why that problem only appears on a farp ? What the heck is going on there ? =( I keep on posting in HDR thread. Also bug only happens at night, starting from a FARP at daytime is fine.

I tested a little more around. The cockpit light bug only happens when starting from a FARP. From runway it's all good. It's like this: Mission loads, Screen appears, FARP is lightened, I push PAUSE to start, FARP light goes out, i start battery, flip the cockpitlight switch (K) but the cockpit stays dark. Also tested without FARP-Mod but no change.

I have a problem with the lightening in night missions, for example the first one in "Deployment". The big cockpit light and nightvision lightning don't work. Panel lightening works but the switches keep black as the darkest night. Also the models keep being black from outside when illuminated. When I make a mission in the Editor the cockpit lights work correct. Is the Deployment mission "alarm" designed that way or is it a bug that I have ? Here some screens:

Can you upload that skin ?

You have a reason to not install the new one ? Could understand if you have very slow internet but otherwise why not install the new one ?

Thank you very much :D Captain Cheesecake now is "undercover"

Awesome mod, only changed the strap-buckles to a darker red instead of orange =)

Because I am annoyed by the cheese-cake face pilot when I watch from external view, I would like to know if there is a way to remove the model or where I can find the texture of the pilot's head/skin to edit it.

Oh this one should go to DCS Addons ^^ Also installed a new russian camosuit mod and it's looking better now. But the head seen from the front still looks like a big cheese-cake face =P From the sites it's looking good.

Is there any mod which modifies the look of the pilot ? I just don't like to look at him from the external view. Reminds me of an action figure. Would be freakin' awesome if a nice modder could add more details and cover the rest of his face. Armed Assault 2 Ru Pilot maybe inspire someone =>

Ah yea GOW and Deployment are two different ones @.@ Thx I'll try that =)

Thought the new Georgian Oil of War 1.1 campaign does this better. Actually I'm playing the old one because I finished this annyoing first mission and didn't want to do it again like you =>

Stuttering caused by missiles... that is strange =(

Was it really neccessary to destroy someones home ? xD Missions sounds interesting will give it a try.

Had a Q9550 before. There is need to overclock until you're performance is always higher then 60fps. It depends on the performance you're expecting. If you are happy with 20fps in big scenes which for me is just to slow and stuttery or if you normally play at high and fluent fps. It's just my oppinion. But with Q9550 at stock speeds I had around 20/25 fps when starting the mission "Altitude" for example. I couldn't stand that, my eyes couldn't so I OCed it to 3.8Ghz and it jumped up to 40fps and everything was fine. Or Armed Assault 2 cause it really eats your CPU power. I ran different benchmark scenes in that game and compared my CPU at 3 Ghz against 4.2Ghz and difference was ~30% Performance. FPS increased from stuttering and not fluent jumping between 30 and 50 to always fluent 60 fps. Would I have compared it with 2.67Ghz stock speed performance boost would even been higher. I mean overclocking CPU is always a good thing, all games/prgrams will run faster. Is no negative about it, a bit more power consumption, yes, install an ernergy-saving lamp in your living room to compensate and it's fine. Know what I mean. As long as you keep it low like 3.4Ghz for example it won't get hot either. It's just positive overall. Only con is that Intel won't get their big profit because you spent 260$ for an i7 920 OCed to 3.4Ghz which is now equal to their 1200$ i7 965 running at 3.4ghz, too. Because you got a crazy high end system I would expect that you are normally playing games at always fluent 60fps or even more if you don't use vsync and 20/30 fps then in DCS looks for you like stuttering. You know, just test it there is nothing to loose. You can use Coretemp to check that, too (http://www.alcpu.com/CoreTemp/ ) . Also why should only DCS heat it up to cause stutter ? A few weeks ago my PC-room, which is located under the roof, had around 35-40°C and it doesn't caused any stutter or a big heat change, 5°C maximum. Also stuttering would occure after a time, lets say 10 or 20 minutes if this was the case, and could only be caused by graphics cards cause CPU turns it self off when getting to temperature limit. Hot graphics cards would also cause graphical artifacts besides that DCS maybe uses 10% of the power of two GTX285. If my explanation of overclocking was too difficult just google "Core i7 overclocking tutorial" and there will be tons of infos for you. greets Cionara

Sounds interesting keep us up =)

Yea inner fuel pumps cause the fuel tanks are on the inner hardpoint and if you got them on the outer one day, turn on the outer fuel pumps ;-)

Just test if it gets better when you overclock to 3.4Ghz. The CPU will only get hotter when you turn up the voltage but I think you can do 3.4 without having to change it. And when you now have Hyperthreading enabled, and then deactivate it your CPU gets cooler and you got some space for overcloking. In fact you only have to overclock to 3.2Ghz because the i7 Turbomode will boost it to 3.4ghz automatic. Just follow the instructions in the tutorial. I think I didn't post the best one. I know a very fine tutorial but it's german. I will just translate it: Overcloking takes place in the BIOS. I give people who are new to overcloking the advice to write the following rules on a paper so they won't do anything wrong. - The Uncore-Clock has to be twice as much as the effective memory clock. e.G. you got DDR3-1600 Memory (Set to 1600MHz of course) the UCLK (Uncoreclock) has to be 3200 or higher. - The QPI-Clock has to be higher then the UCLK ( In general the QPI is always higher because it gets raised automatic by overclocking) About the voltages. Change as much as voltages as you can away from [AUTO] to the default values. The default values are normally shown on the right side in the BIOS. ( If you do not, the System will automatically raise the voltages when overcloking which is not neccessary and could be dangerous for some hardware) First you should note your current bios settings. You got a Asus mainboard, Maybe you can even save them as a profile on the mainboard. I can do that with my Asus board by pressing F11 in the bios I think, that's very nice. Then you should deactivate the CPU features called Speedstep and EIST (I advice to turn Hyperthreading of, too). Change the PCI-E-Clock from Auto to the default 100. Set the Vcore (CPU Voltage) to 1.25V. Ok now let's start. For 3.2Ghz you need a BLCK (Basis Clock) of 160 which usaully needs a QPI-Voltage of 1.3V. So set BCLK to 160 and QPI to 1.25. the Multiplicator should be 20. Now look if the DD3 Memory runs in it's specification (means not higher then 1600mhz, if it does, use a lower Memory-Multiplier) and that the Uncore-Clock is twice as much as the Memory Clock. Save the settings, reboot your computer. Use the tool "Prime95" which you run in the "SmallFFTS mode" to look if the PC is stable and use the tool "Coretemp" to see how hot it gets. If it ain't get hotter then 65°C it's ok. Try that out and report how it worked. If your PC crashes change the Vcore (CPU voltage not the QPI) from 1.25 to 1.3 and try again. If you really have bad luck and if your computer won't even boot, turn it off and clear CMOS. This are 2 pins you have to contact with screwdriver for some seconds, more information in your mainboard manual. But don't be scared this shouldn't happen and if your PC case is open it takes 5 seconds to contact the pins and it's all like it was before.

Your system is very nice. Did you overclock it ? Because DCS uses only one core and at stock speeds your i7 920 won't be better then a 3,2Ghz Pentium 4 in this sim. And a 700$ i7 940 won't be better, too. But luckily the i7 920 is very easy to overclock. I got mine to 4.3Ghz from 2.67Ghz stock. I have it watercooled but I think you can easily OC it to 3.6Ghz with a new CPU fan if you ain't already got a good one. Maybe 3.4Ghz with intel cpu cooler. I also give you the advice to turn HT (Hyperthreading) off in the BIOS. It simulates 4 additional cores, so it's 8 then but there ain't no games which benefit from it, they often even loose some. HT also heats up the CPU a lot and takes more voltage. Here is a nice Tutorial for i7 OC: http://www.bit-tech.net/hardware/cpus/2008/11/06/overclocking-intel-core-i7-920/1 And you won't loose warranty because nobody (not even Intel) can proove if you OCed your CPU.

But only if you're graphics card is not tha bomb. My frames drop from 160 to 130 when enabling it but only when there's nothing to do for my CPU. As long as my FPS don't drop lower then 50/60. At start of the mission altitude for example my frames drop from 50 to 49 when I turn it on. Basically no difference in performance then. I would also recommend to not use the best AA for example like 16xQ. You can't see it but it costs a lot of performance. Three times more then this here. For me 4xAA and 8xAF removes all edges and doesn't eat performance like 16xAA and 16xAF. Same goes for Super Sampling Anti Aliasing mode. Multisampling is a lot faster and you can't see a difference. greets Cionara

Haha ok, thank you very much :D

No pedals included, right ? Very expensive without pedals..

Thank you for watching =) Ok cool not my fault. But had it two times yesterday. Was really frustrating to get blown up because of a road.