PiedDroit

Yeah that's the big question - when? If that comes within 1-2 years I'll wait, otherwise I'll probably get a CV1... FOVE has more pixel and is releasing a dev kit soon, so it might be the ticket. I hope Oculus or HTC will make an annoucement before the consumer version is released. So, for the initial question, if you really want to do the dive now, get it, it's worth it - if you're on the edge, maybe you can wait a little bit more just in case :D

According to most reviews here it's definitely worth it (just look up the forums). A bit low on resolution but immersion is top-notch (I tried the CV1 for about 3 hours). However, if you are patient and/or limited on budget you should wait for the next iteration. You'll get more resolution (hopefully) - or get 1st generation devices cheaper on the second hand market. I am myself waiting to get something with higher res, as this is a big investment (my old GTX680 won't stand a chance so I need to upgrade the GC as well), and I won't be able to upgrade anytime soon after that.

Hi jcdenton, in summary, avoid giving large cyclic inputs while your rotor is unloaded to avoid the mast bumping. It happens mainly on ground and during flight after a climb. Cheers

Hello, I know it's an old thread but I only started using the F-5E now. On the A1 vs A2 question: A1: "Start to fire one projectile time-of-fligh before the pipper reaches the target future position", "The task is to project target and pipper motion to a point of intersection and to fire approximately one projectile time-of -flight before intersection would occur." This looks like a description of "historical" type sight, which means it's showing where the bullets you would have shot X seconds ago would be now. Where X is the TOF. Since it seems to try showing the actual bullet flight path, it is more suitable for snapshot. What you need to do is to predict when the target will cross the path, and shoot to take in account the time of flight of the bullets. For example: my time of flight is 1 second. I'm maneuvering so I know that the target will cross the piper. I need to shoot 1 second before the target meets the piper. Note that this is how the M-2000C's sight is working (picture it without the snake). A2: "The pipper is displayed one projectile time-of-flight from the gun line for the rate the attack aircraft is turning and target range." This is LCOS sight, it only computes lead, which means it's showing where the bullets you shoot NOW would be in X seconds, taking in account the attack aircraft aircraft's motion and the range, where X is the computed TOF. With this sight, you need to shoot when you have achived tracking and target is on top of the piper, if the target doesn't maneuver it will be hit. Hope this helps

There are two switches to set, did you set them both? One switch is on the left wall next to the white chute lever (not very visible). The other switch has three position, it must be in second or third position (third position add refueling light). This switch is right below the taxi/landing light switch.

It doesn't matter - if you have only one pair of pods then always select both EXT and INT, this way you're sure it will fire allright. Selecting INT or EXT exclusively only makes sense when you have 4 pods and you want to save ammo.

I'd suggest posting a short track ;)

mast bumping maybe?

usually the best way to deal with any game breaking configuration is to delete the options.lua in your \Saved Games\DCS\ folder (not sure which sub folder), or even delete the entire folder (which is then regenerated to default values).

That would be the issue, try without the snakeeyes. I think you can't mix different types of bombs nor mix bomb and rockets, the computer only supports one type. Also if you load 4 pods of rockets, if only half of them go off it is not a bug, you need to select both EXT and INT ;)

What is your loadout? One possible issue is that you loaded something not valid. I just tried with 2 pods (internal and external) and 4 pods, it worked.

Hi baltic_dragon, if I may, I'll answer this as well. I just finished M13 ("version": "1.5.5.60565.216"), all chatter OK, outro too. The bug we currently have on INS update is still there but it doesn't disrupt the mission (one can just ignore that part, it still works). More details with minor spoilers:

cool

Good format, no nonsense/lengthy talk, straight to the point - excellent! I like the format :thumbup: To make it perfect, I'd suggest to add a short textual description for the non obvious items (example: the "AG designate" button for CCRP). Or even better, a one liner for each action in the description.

Did you set your resolution in the "system" section? Normally the options pages don't fill the whole screen (i.e. the options pages are smaller and don't fill the whole space).

I think it should be OK, as you can still move you eyes to the right and thus see the entire screen in the Oculus. I mean, it's not like if you cover half of the lenses, as your eyes can move around, so what you can do is put what you want to focus on on the right side of the screen and then move your eyes to the right, this way you will have the whole picture in view, for both eyes. That said, I don't remember how the focus on the edges of the screen is in the oculus, Rift users should be able to tell at which point looking on the side is practical in terms of focus. If focus is good all the way to the edges of the lenses, then you should be able to use it normally.

Usually that kind of filtering is done at a different level in the system (if done at all). For example, let's say you have a sensor that has a fixed set of parameters (which may or may not be configurable), in return the sensor will output everything it find that falls into those parameters. After that (at the next level), all the sensor's input will be grouped together, tracked (i.e. the system will try to link one detection to another detection in the previous cycle). Detections will then be confirmed or ignored, based on the track history, that the raw sensor doesn't know about. For example, a detection that has is not moving over time, or has a calculated speed that does not correspond to it's predicted path, or unrealistic speed, whatever. Filtering by sun position would fall into those categories. But due to the number of things that could go wrong with this approach (aircraft attitude, time of day, geo localisation, weather), my bet is that there is no such thing in the DDM, only raw filtering based on strength (and maybe spectrum). But why not :D

Certainly not linked to sun's position at a given time, sensors aren't that smart :D Flitering would be done based on size/intensity => anything that is bigger/brighter than X or is in whatever spectrum is filtered out, that's it. I worked on sensors, not optical, but I guess the principle is the same, you know what you're looking for (in terms of size, spectrum, etc), anything that falls out those parameters is ignored.

OK thanks. I flew it and finished it succesfully, I think M07 didn't work at first because some flags weren't set at the beginning of the flight, due to the offset.

Ok, I think I found the issue... I had forgotten to enter the initial position in the INS during startup, so my whole flight was offset (at least until I got the coordinates, were I did an INS update, seeing that I was way off)... :D

Maybe I cut the corners on RTB, I'll try again with strictly following flight plan on return from WP4 (i.e. 3-2-5-6-7)... After having SABRE takeoff, did you have to complete other tasks? I didn't. Thanks

Hello, I'd like to know if the bug affecting the triggers could prevent M07 to finish. I could hear TWO most of the time, however after completing all tasks successfully, I got the dialog saying flight is RTB, little chit-chat on the way home (about doing CSAR with the Mirage), but after landing nothing happens, even after taxiing to designated spot. If I quit, mission is deemed a failure (can't progress). Had this twice, I don't want to fly it again if there is a mission-breaking bug. On first try my wingman ejected due to lack of fuel (even though I told him to RTB), so on second try I made sure he hit the tanker before going back, I also waited for him to land, but no dice. Thanks!

Hello, for info I had the exact same issue (Requires another product), which got solved too, eventually. The "BUY" button for the F-5E aggressors campaign didn't show up until I got to the NTTR store page (which was showing "BOUGHT" as expected) and pressed the "SHOW SERIAL NUMBERS" button. Maybe it's not related and it was a mere coincidence. It's worth trying in case somebody else has the issue.

Good news indeed! Thanks for sharing it, I'll be looking forward to it (I'm eager to get the Harrier as well) :thumbup:

I totally agree to that! We need content. Actually there was a little poll run by Wags (What do you want to see most in DCS World?) a while ago and the dynamic campaign system was what came largely ahead, so they're pretty much are aware of this, no doubt we'll see something happening after the F/A-18C is out. On the M-2000C I already done all the trainings, the campaign seems really good, I'm looking forward to go in deeper (I only completed a handful of missions so far).