Lange_666
-
Posts
3965 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Lange_666
-
-
I am glad to see that I am not alone in facing this issue. But I want to learn and avoid using any kind of labels. Especially as u see in some of the videos (Ralfi's)...people are so adept at finding targets blind.
And how many times have they flown the same mission over and over again with the same targets always on the same locations before making the actual video? Once you know that info, spotting them is fairly easy.
If you don't have any info at all, not from the briefing (a lot of missions suck big time in briefings), not from the F-10 map etc... then it's far from easy to spot them first flying that mission.
-
Its embarassing to admit, but I have been playing ed sims since the flanker days and I hate to admit that only now am I learning to play without labels on.
I feel it's not that embarrasing as you think it is. I used to fly around with labels a lot too, just to be able to build me a picture of my surrounding world. Then i ended up 51th server flying A-10A missions and there where no labels anymore. Hard at first but once you get used to it, you really didn't need them. Up until FC1 targets where always visible as a black spot, even from miles away. Couldn't see them sitting between the building of a town, no problem, just fly the mission without buildings once to give you an idea on where they were and then refly the same mission with buildings on. It was a bit like using the map.
From FC2, targets were not black spots anymore and got a more camo look which didn't make things easier. But since flying on the 51th servers, i stopped flying with labels on.
Like EtherealN says, technical aspects of your setup can make a difference. There is more shimmering with TrackIR on as it is without (just put TIR on pause while looking at a fence and you know what i'm talking about). And more shimmering can hide small objects, certainly when they are only a few pixels big. I pause my TrackIR a lot to get a stable picture.
Also zooming can make a big difference. Zooming is in fact as big as a cheat as labels are. There is nobody on earth who can zoom like flightsims can (hell, even Lee Majors did not had that kinda zoom in The Six Million Dollar Man). But since zooming is available, use it to your advantage to find targets. Once you get the hang of flying without labels, the reward is much bigger.
A good way to learn is to go online, download the mission, edit it with the mission editor so you can see everything, make hidden targets visible on the map, print it, set everything to default mission standard again and then use this info as a briefing and try to find the targets. Nice training to get you going.
-
Coming from a Sidewinder myself i must admit that a twister stick, although unreal, is a very good substitute for pedals. I really liked it (and i still have it but on shelve somewhere) and i still find today that i could fly more precise with the twister as rudder then with actual rudder pedals.
But i gave up the moment M$ decided to not support it anymore (software wise) in WinXP which directly cut the use of the buttons by 50%. Got myself a TM Cougar and after making my own gimbal mod decided to go for something more professional and installed one of IJ's first U2 mods. Been a superb piece of hardware since. Only want to trade for a Warthog if it would die.
As rudder i'm using CH pedals and i can only second the quote below:
CH pedals. Indestructible. That's about it. Pedals are a bit too close together, (this issue is slightly more aggravating when you have size 14 feet) and look like the footrests on wheelchairs. Re-defines butt ugly. That said- they are indestructible. -
[i also want to purchase the latest FC3 when it comes out. Is it going to be distributed on disk?
Because of the way DCS World and the modules are updated now, it's useless to distribute them on disk. Your disk would become useless after the first major upgrade.
-
ED's minimum system requirements to run DCS World (honestly, even with their recommended requirements you have to run it on low settings and even then it may run like shit):
Operating system: Windows XP, Vista or 7; Processor: Core 2 Duo 2.0 GHz; Memory: 3 GB; Free hard disk space: 7 GB; Video: 512 MB RAM card, DirectX 9 - compatible; Sound: DirectX 9.0c - compatible; requires internet activation.
You match the "minimum" requirements for the OS (Windows Vista) and the CPU but your system is below the "minimum" requirements for RAM (2GB instead of 3) and video RAM (yours is 256MB instead of the required 512MB).
So i think Eight Ball from Bubbelgium has some sort of point...
-
Have my OS on harddisk and flightsims on an SSD (can't make gameplay stutterfree when OS is on SSD with my current setup). Al other stuff is still on harddisk.
SSD's may have become cheaper but i don't find them cheap yet.
-
I think you ask too much. It's best not to have it included if you don't want your head chopped off by one of the rotors. You might be able to dodge the first one but you would be a very lucky bastard if you dodged the second one too...
-
Just get one and test it. If you get a hard-on it works, if not, re-sell it on ebay.
-
Same here, it's been there since at least early 1.2.2.
Just like FoxFireTwoOne, it's showing just after pressing the "Fly" button.
It's only visible for a second or so so i don't bother, far from a jobstopper, nothing important.
-
You don't need to activate DCS World because it's a free program.
You can deactivate modules first before you re-install everything by going to your DCS World installation directory: DCS World\Mods\Aircraft and there select the module you want to deactivate (A-10C in your case), then go to bin and run the file a10_protect.exe (DCS World\Mods\Aircraft\A-10C\bin)
You will get a de-activation screen, the same as your activation screen. Follow instructions and you are good.
-
Will FC3 come as a boxed version soon?
If you look at the way updates work right now, getting aboxed version is pretty useless (besides having a nice box sitting on your shelf doing nothing). So making a boxed version is pretty useless.
Reason: Once you install a newer version of DCS World from scratch, older modules are not longer accepted and you need to have the FC3 module with the same version number as the DCS World version you just installed. This FC3 module will be available for download as soon as the new version of DCS Worls is offered for download.
If you don't have to re-install DCS World and make use of the autoupdater, everything is updated automatically, included the modules.
Note: The only thing i feel they need to change is the bandwidth of their own server. Counting on a torrent for distribution is a bit cheap imho (but works great as long as there are enough seeders).
-
The cheapest will do.
-
1. Lock On (FC3):
-I'm maybe going to buy LO FC3. To install it, I need the Lock On from 2003, right?
Yes
-When I maybe have buyed FC3, do I have (in one installation) all modules, and flyable aircrafts from FC1 and FC2, too?No, you only have the FC3 module (so no A-10C, KA-50, P-51 and no Combined Arms). But you get all flyable aircraft from FC1 and FC2.
As far as they are updated, like the new improved F-15 pit. But then again... FC3 is still in BETA stage.And have they then a up-to-date graphic (all planes!)3. How do I install DCS: World?-I have a Steam-copy from A-10C installed. I have read, that I have to activate A-10C after I have installed DCS: World, but how, when A-10C is already installed?
Download latest DCS World and install it. You get DCS World and the Su-25T as flyable aircraft.
Download latest A-10C module and select a mission to fly the A-10C. While this is loading, a enter-key screen will pop-up. Just enter your A-10C code and you're fine.
If I install FC3 (when have bought it), it automatically detectes DCS:World, right?Yes
-
No worries man.
Tu doit telecharger les modules A-10C et KA-50 version 1.2.2.7570 et installer les deux modules dans un version DCS World avec le même nummero de version.
Link: A-10C
Link: KA-50
Donc: Quand tu as installer DCS World 1.2.2.5970 et faits l'upgrade vers 1.2.2.7570 (ou installer version 1.2.2.7570 sans upgrade), tu sais installer les modules 1.2.2.7570 dans DCS World. Simple comme bonjour....
Edit
Totally overlooked the part that your DCS World is out of date as well (version 1.2.1). Download the newest version here.Uninstall DCS World, install the new version, then the modules.
J'ai faits le même erreur...:cry:
-
It also reveals some extra (minor) bugs.
- When the A-10's shine their nosewheel light on a bunch of the trees, these trees a lighted upon from the front while the A-10's nosewheel light shine on them from the back.
- Sound: If you use the flyby view on the first and second A-10 that take-off, their flyby sound is chopped by that of the nearby heli's.
Also, i got a headache looking from pilot view the first time i watched the track. So hectic... didn't you had a soar neck or so after making the track?
And... the runway is too short for the B1-B to take off propherly.
-
But impossible to upgraded my "DCS World" Version 1.2.2.7570 to 1.2.2.7286...
I trying the options: "Update DCS World" or "Repair DCS WORLD" but nothing, No work...
So I've try to installed my A-10C V1.2.2 and BS2 V1.2.2 but impossible also because my "DCS World" is too old.
Upgrading from 1.2.27570 to 1.2.2.7286 actually isn't an upgrade but rather a downgrade.
Do you really get a message that your DCS Words is too old?
I believe that for a succesfull install and an upcoming upgrade, you need to have the DCW World and the modules you own to have the same version number will it work correctly.
If the DCS W versions is 1.2.2.7268 when installed, then the modules have to be 1.2.2.7268 too. If that is done, you should be able to upgrade to 1.2.2.7570.
But if you installed 1.2.2.7268 and upgraded to 1.2.2.7570 without installing the 1.2.2.7268 modules, i guess that you can't install them into 1.2.2.7570 anymore (hence the error) and that you need to download the 1.2.2.7570 modules to make it work.
Or install everything from scratch but only the latest stuff 1.2.2.7570. Then you don't need any update at all.
-
At your service... just scroll up a bit or click below which warps you right at it...
http://forums.eagle.ru/showpost.php?p=1611266&postcount=21
Edit: thread jumped to another page so instead of scrolling up... it's better to use the provided links...
-
After the roll back to 306.97 WHQL all was fine again but not for that long.
Today i sufferend again from the "videodriver not responding but recovered" error and a bit later, when launching TrackIR, the screen went black with no recovery besides hardreseting the PC.
This leaves me with a hardware problem i guess instead of a driver problem.
Haven't figured it out yet what causes this but reading through forums which make note of the same error points into the direction of the videocard. Those who had the same error changed their videocard in the end to solve the problem.
But i'm still a bit uncertain that this is the case because under load (playing a videogame) the videocrad never crashed on me. It only does this while some applications are started: TrackIR, GameBoosters Analyzer, Opera browers while loading a video from Youtube.
Also, when it crashes, as far as i can check, voltages and temps are all normal and well within range (under load, the temperature even doubles).
What bugs me a bit is that the videocard (sometimes) stops sending a signal to the screen when TrackIR is loaded and more... on the moment when the TrackIR device should be activated. If i unplug it and only run the TrackIR software, the videocard never looses it's signal.
This makes me think it's more of a power problem but... the videocard uses different outlets on the powersupply then the motherboard does. Or it must be that the PCI bus is shortly interrupted when the TrackIR comes on.
But then again... that does not explain the problem with GameBoosters Analyzer or Opera (which don't use extra power like TrackIR does).
So i'm still a bit in the dark on what causes the hang-ups: videocard or powersupply (or maybe the motherboard in general but that's only option 3 atm)...:cry:
Solved: Driver issue, so not a hardware problem. Currently at a new install of 306.97 WHQL since thursday evening, not a single error anymore, no more freezes either.
-
I have did a complete un-install and re-install and to the same result
There are some more questions:
Did you install like you did before, ie an older DCS World (like 1.2.0 or so) and then let it update itself to 1.2.2?
If you installed it this way, did you try the older version before you updated it (remove your internet connection to prevent the auto update)?
Or did you download the 1.2.2 version and install that one from scratch?
Did you run DCS World without any modules installed (clean DCS World install and just fly the Su-25 as a test)?
Did you try the above with a cleared Saved Games directory or did you leave everything in there and installed DCS over it?
-
In fact, DCS sound is offloaded onto a second core.
-
Wrong error code in the above link (Not your fault Wolf Rider, the topic starter made a little error in his post). It's 0xc000007b, not 0x0000007b which gives a different error:
The application was unable to install correctly (0xc000007b).
One of the solutions refers to a bad image error on the installation file so maybe the installer is corrupt (found this for another program, not DCS), another points to the .NET Framework etc...
In general i found that it mostly says that something needs to be repaired so a corrupt file ma be the culprit here.
-
I just went ingame after playing around a bit with either "Clamp" or "Allow" and i don't see difference anymore between the two. Maybe something has changed between early 300 versions and 306.97 which i have installed right now.
BTW: there are new beta's out 310.61
-
Yes but then his ingame setting should be set to certain value instead of off.Your AA setting needs to be Application Controlled (not Overide Program setting)That's why i said above that it's a mess. Sometimes you have to set it ingame, sometimes you have to set it in the control panel, sometimes you can set it to override and sometimes override doesn't work. And in most cases you only find out by testing after each update.
I always thought that this setting had to do with the GPU (didn't really dig into it in the past) but it seems that it's about the CPU.and setting Threaded Optimisation to Off (instead of Auto) helps immensleyFrom TweakGuides: Threaded Optimization: Controls the use of multithreaded optimization for all 3D games on systems with multi-core/HyperThreaded CPUs. The available settings are Auto, On and Off. I strongly recommend the default option of Auto, allowing the drivers to set this appropriately for various games based on your hardware. Only turn Off for troubleshooting purposes if you believe a particular (older) game is not compatible with multi-core CPUs, and only set to On if troubleshooting to see if it improves performance in a recent game.
But your comment made me test it again and honstely, i don't see any difference between Auto, On or Off (but i can only comment on my own system of course).
Since his VSync setting is set to 1/2 the refreshrate, there is no use in setting it to 60 (assuming that the refreshrate is 60Hz). Lowering to 30, either through nVidia's inspector or MaxFPS = 30 in the graphics.cfg files does the same thing.set the FPS limiter to the same as your monitor Hz.Edit: see above: msalama's refreshrate seems to be 70 so 35 is a perfect value!
For those who experience LCD motionstutter by framerate drops below the monitors refreshrate (everybody does have it but not everybody sees it or cares about it), setting the VSync rate to Adaptive at 1/2 refreshrate does wonders. The only drawback is that you now have some motion stutter in the TGP or MAV MFD screens, like the refreshrate for the MFD's dropped to 1/4 instead of 1/2. But it's a minor drawback, at least for me.
Also, mslama's Max Pre-render setting is 8 where everybody says it should be set to 0 (you can't do that anymore since the 300 drivers saw the light of day, minimum is now 1).
I played around a lot with this setting in the past and really didn't see much of a difference between default (3) or min (now 1). But when i set it to anything higher then 4 i saw a difference but worse so i'm a bit amazed that msalama setting is 8!!
Same goes for Texture Filtering: Negative LOD Bias. His setting is still on "Clamp". Now on every driver below 300 i had to set this to "Clamp" too because when i had it set to default "Allow" (below 300 drivers the default was "Allow", now it's the other way around), the images looked not that good. But since the 300 release i have to set this to "Allow" in order to get the best image quality.
-
I had the same problem with my last pc build. I thought there was nothing i hadn't tried until i set my CPU back to stock values. It seems that the CPU OC i did played havoc on my GPU. Running smooth for 2 months now without OC's.
Oh, and the build before this one i had it too, but slightly underclocking my GPU solved the problem. It is also said that you can try to up the voltage on your GPU a bit, but i haven't tried that.
Good luck!
Nothing over- or underclocked atm (i always keep things running at stock speed). But i will find out in the end, no worries...:pilotfly:
Refund?
in Payment and Activation
Posted
Well, as for me, i don't need a refund but i can't say i'm thrilled either. It might be an almost impeccable P-51 sim, the immersion of the P-51 goes down the drain in the modern world it has to fly in. See it as putting the A-10C into Rise Of Flight. It's an almost impeccable A-10C sim but it will be totally misplaced there. So the same goes for the P-51. Nice but useless.
PS: Can't wait until some 3th party gang put up some Wing Commander stuff in DCS World. Now that must be fun.... NOT.