exil

Same problem here using the HP Reverb!

Thank you for posting! Real World Pilot here too, but with no Gazelle experience. And therefore got somehow beat down by some guys here for criticizing the flight model more than a year ago. Their argument was, that the FM was checked by some french airforce guys and that they would like the FM. I could never believe that. It just didnt (and still doesn't) behave like a real chopper. Hope Polychop will fix this somehow, because the chopper itself is a great add on in the world of dcs! I wish them all the best in making this a great chopper.

Hallo, kann mir jemand annähernd sagen, mit welcher performance ich bei der Reverb mit einer Gtx 1080 rechnen kann? Habe aktuell die rift s, bin prinzipiell zufrieden, aber häufiger das Problem, dass mein Rechner die Displayport Verbindung verliert. Auch eine Pci-e USB hat nichts gebracht.

Hey Sandman, did you find a fix for it? Having the same problem too. My Room is very bright (two windows) but the rift only seems to start DCS with 3DOF. Thanks!

Perfect! That worked! Thank you very much dark_wood. That saved me a lot of time! Out of curiousity: What does the semicolon do?

Gentlemen, i need some help with a "time since flag" trigger. I did something like this: ONCE -> some condition -> do script: if Unit.getByName('unitxxx'):isActive() then trigger.action.setUserFlag(10, true) end followed by: SWITCHED CONDITION -> time since flag (10, 30) -> activate Group (yyy) But actually nothing happens. If i exchage "time since flag" with "flag is true (10)" everything is working fine. Any help would be appriciated!

Cool stuff! Thanks!

Gents, i hijacked a code from ajax from the following thread to get some kind of FastRope action working. HERE I added a line "hover" to simulate the helicopter hovering. Everything is working fine so far. local function anyUnitLandedInZone(units, zone, checkLanded, checkStopped) local stopSpeed = 1.0 -- m/s local landed = false local hover = false local inZone = false local alive = false local stopped = false local i for i=1,#units do local group = Group.getByName(units[i]) if group then local unit = group:getUnit(1) if unit and unit:isActive() then -- is unit in zone? local unitPos = unit:getPoint() local z = trigger.misc.getZone(zone) if z then local dx = unitPos.x - z.point.x local dy = unitPos.z - z.point.z local d = math.sqrt(dx*dx + dy*dy) if d < z.radius then inZone = true end end -- has unit landed? local inAir = unit:inAir() if not inAir then landed = true end -- check if unit is in hover local pos = unit:getPoint() local agl = pos.y - land.getHeight({x=pos.x, y = pos.z}) if (agl > 3 and agl < 18) then hover = true end -- is unit still alive? local life = unit:getLife() if life > 1 then alive = true end -- has unit stopped? local v = unit:getVelocity() local s = math.sqrt(v.x*v.x + v.y*v.y + v.z*v.z) if s < stopSpeed then stopped = true end end --return true if conditions met if (landed or hover) and inZone and alive and stopped then return true end end end end return anyUnitLandedInZone( { 'JOLLY01' , 'Cicada-2' , 'Cicada-3' , 'Cicada-4' , 'Vespa-1-Lead' , 'Vespa-2' , 'Vespa-3' , 'Vespa-4' , 'Vulture-1-Lead' , 'Vulture-2' , 'Vulture-3' , 'Vulture-4' , } , 'FASTROPE01', false, false ) To get a fastrope working properly, i want to add a certain amount of time, where the helo needs to hover within a specific height bounderies (see code) for at least xx amount of seconds to simulate the troops roping. I tried variations with "timer.scheduleFunction" but doesn't seem to get it to work. Any advise would be appriciated!

That should do the job perfectly...The only thing i'm concerned about is the 8BG RAM. But just for trying out missions with low settings it should be fine. In any case you could upgrade to 16GB later on anyways.

Really curious how this baby will handle VR in DCS. A lot of 1080p tests have shown slight less performant results that the 2080. But i just read a test for 5K, where the R7 was better than the 2080 in most of cases. VR, especially in MP uses all of my 8GB VRAM of my 1080. So the 16GB VRAM of the R7 seem to be a good option. I think right now it's a bit too pricey. AMD should sell it for 600€. That would be an statement for Nvidia and a lot more people would be convinced to buy AMD again.

Can't really tell since the ME isn't really demanding itself. What you need the power for is in game testing (see if AI behaves correctly and if all the triggers work). Idk if a Intel graphics chip will be enough, but a 1050 will be overpowered i guess. As i said, i'm using a 2016 Laptop with an Nvidia GTX 960M. And that is really enough power for testing. Is the only purpose of this laptop to make missions in the ME or will you play other games (Battlefield or stuff like that) as well?

Well, i have a 2016 Acer Aspire Nitro with a NVDIA 960M card in it. For mission building absolutely sufficient. I even used to play DCS on it. The Editor itself isn't very demanding, only if you test your missions. But as you said, you can allways lower the specs for testing. I just would recommend a SSD for shorter loading times.

Same problem here under WIN 10. VR and non-VR. I currently deinstalled PG Map and am reinstalling it again. Will report if this helps.

Minimum System Requirements Operating system Windows® 10 64bits Processor Intel® core™ i7-7700 or AMD Ryzen™ 7 2700X Graphics NVIDIA® GeForce® GTX1080 Memory 16GB Lol...no way this thing will ever work in DCS with current gear. Even the new to come GTX (RTX) 2080 will be enough to manage this thing! But it's good to see that VR is still improving! Keep the HMDs coming ;)

Keep your head up and fight!!! Get well soon!

Wow! Just wow! Didn't know it is that bad!

+1 SRS is (besides 2.5) one of the best things that happened to DCS in the past! The immersion on blueflag with SRS is just perfect!

Awesome job on the FM again! I don't exactly know what is different now and what you tweaked, but it feels more smooth and natural now (only tested the minigun version after 2.5.1 beta release)! From the worst chopper in the past to my favourite chopper in the present! That transition was only possible because of you guys patiently tweaking the FM. Great job! Thank you!

Didn't mean your system, i was refering to my system with my R5 1600 and the 1080 :smilewink: I spend 190€ for the CPU and less than 500€ for the 1080...good ol times (Summer 2017 :cry:)

Nice comparison! Thank you very much for your work! A VR-Test would also be cool, but the results given in your test suggests that even with a 2700X the bottleneck in VR will be the GPU. Besides the better min FPS i don't exspect any major improvement over the 1700X. I have an Ryzen 5 1600 non X running at 3700Mhz and a MSI 1080 Gaming X (non ti) but that combo works out pretty well in VR. So, with one of the cheapest CPU i can run DCS VR very decent! So all in all it's a nice confirmation, that the choice to buy a cheap Ryzen instead of a not so cheap 7700K was a good one ;)

Wow!!! Vielen Dank für die Mühe...ich studiere das Teil mal fleißig!

Tested: All i can say is great job! Finally the pitch and roll axis works as intended and it feels like a real chopper now! Superb work!!!

So, with the latest 2.5 Changelog: https://forums.eagle.ru/showthread.php?p=3423375#post3423375 Are the latest Gazelle changes implemented or do we have to wait for an other ED update?

Natürlich...vielleicht wäre das was für die Zukunft wenn Vulcan kommt und (hoffentlich) den erwarteten Performancegewinn bringt. Gerade im Heli im Tiefflug kommt man sich bedingt durch die wirklich großen Bäume seeeehr lahm vor. Aber lieber lahmes Fluggefühl als lahme Frames.

NVG-compatible cockpit doesn't nessesarely mean a cockpit where you can read the gauges through your goggles. It mostly means, that you can dim down the instrument panel lightning as it would otherwise block out your goggles due to the light it produces.