Jump to content

Bourrinopathe

Members
  • Posts

    1004
  • Joined

  • Last visited

Posts posted by Bourrinopathe

  1. I'll be picking up a 970 m.2 from which I want to run DCS.

     

    Q: Is it as simple as dragging the whole 'Eagle Dynamics' folder across and creating new shortcuts or is there more involved?

     

    What about the DCS stuff that lives in the 'Saved Games/DCS' folder (config, missions etc)? Does that need to be migrated too?

     

    It's certainly not a nightmare to migrate the DCS install (to the point I don't remember accurately what I did ^^).

    Iirc I just copied my DCS program folder to the new SSD (non-system, different path from my original install), copied the Saved Games/DCS folder from my backup to my new NVMe SSD and then just fired it up.

    I had to enter my serials as it was a new machine, but that was about it. I paid a visit to the settings and changed a few things.

     

    I think I just updated as usual (using the DCS_updater.exe).

  2. Interesting post and thread. Thanks for all this!

    Similarly to dburne I also recently built a new PC with both 970 EVO and PRO as it's my main professional tool and simming rig.

    The speeds are impressive and if the PRO SSDs are supposed to retain their high speed more consistently than the EVO (MLC V-NAND vs TLC V-NAND) I still have to witness how different they can be.

    SSDs performance slows down as it becomes full, and that's why I chose a 970 PRO as my system and main working storage (so I don't lose speed over time, as it gets filled by files/data).

     

    I'd be curious to see how a possible 970 PRO Plus performs and how noticeable the difference can be compared to the current PRO version.

    At this point, I can only say that both (EVO and PRO) are blazingly fast and I can't tell the difference with my current use (but I didn't push them yet).

     

    DCS is installed on my 970 EVO.

  3. I cannot find information about slider that's marked as "target distance". No official documents has it marked that way.

     

    As stated in my post I'm not sure about this one as I also couldn't find any official info.

    I extrapolated the function from the Su-27 throttle as they're very similar and pilots usually learn how to use standardized controls for efficiency (and versatility) purposes.

     

    The GAF T.O. 1F-MIG29-1 does not show any wheel on the throttle schematics.

     

    15c40942451dc14d9f932422c41577a1.jpg

     

    It might be possible to find some clues in the Пособие по боевому применению document ("Combat Employment") but I didn't studied it thoroughly (yet?) - so I only know ranges are (obviously) mentioned repeatedly.

     

    By the way, if anyone has the 450 pages version for the GAF T.O. 1F-MIG29-1, I'd be very interested in adding it to my collection :thumbup:

     

    ----

     

    The only info I found that would suggest that dented wheel is there is that low quality drawing from a Bosnian (?) MiG-29B document:

    180532961a21b3c0f46d27a9cf451a0d.jpg

  4. @Ragnar65 You could use this video as reference. It's a perfect demonstration of the numbers provided by YoYo.

     

     

    Depending on your hardware, you might want to tweak your pitch axis sensitivity/curve so your pitch attitude is steady during your approach and landing.

     

    I'm sure once you get this right, you'll be able to extrapolate with different configurations.

     

    Happy landings :thumbup:

  5. Here's a quick reference based on DCS visuals:

    c5314d23b1085d0117292f0ea34dfc4e.png

    b9cbdee1a5b0c01b2c8d6254c23394ab.png

     

    Does the 'Break-lock' correspond to 'Return to Search' in DCS controls?

    Does the 'Target Distance' correspond to 'Predicted Target Range Increase/Decrease' for the current module, and is it correctly implemented?

    (I'm not sure about those two and I didn't get the time to check yet)

  6. Yes please!

    I've started learning the M2000 with a friend some weeks ago (despite the fact that I own the module since its beta stage), and I've been surprised I couldn't find the HUD brightness control.

     

    It's just that we had to bring back this beauty after some simple pattern and navigation exercise and the MP server had a mission late in the day, so it ended up in a beautiful sunset.

    Problem is the HUD started to become an annoyance as I/we started to struggle seeing anything beyond the bright display.

    Since then I avoid flying the M2000 anywhere near that time of day.

     

    Is there any news on this?

     

    ----

     

    Ha! Found it!

     

    https://forums.eagle.ru/showpost.php?p=3633827&postcount=619

     

    Witchcraft is happening!

    Yes!

  7. Using the latest OB.

    It seems the L-39C/ZA cockpits are missing the advanced lighting/reflection/relief effects.

    Possibly not applied as the specular textures and normal maps are present in the default textures archive (?).

     

    No (fake) reflections on the instruments glass, no relief on the gunsight knob, no metallic surface effect, etc. All these were visible before.

    It looks bland. :(

  8. I meant useless for the front seat if it's only fitted in the rear cockpit. But I get your point.

    Still, I wouldn't be comfortable using an instrument as complex as this navigation system sitting behind the control stick. A few switches or a compass are fine though.

     

    The only retrofits photos I've seen are modernised dashboards with the GPS in the center or a GPS unit fixed to the right side of the dashboard.

  9. I voted "yes" but I can't see where a NS430 would fit.

     

    It might fit on the rear dashboard below the main instruments but it would then be both unpractical (sitting low, behind the stick) for the rear seat and useless for the front seat pilot which I'm sure is what most of us use.

     

    So it's also a solid "no" if it's not properly integrated.

  10. Thanks for that neat trick guys!

    I just stumbled upon that thread searching for a way to remove a bunch of trees in the scenery.

     

    From my understanding, the trigger removes the whole vector area filled with trees and does not allow any finer control.

    Similarly I don't think there would be a way to add trees unless ED provides a vector tool we could use in the ME.

    That's exactly how it's done in X-Plane World Editor as you can define a polygon filled with a given type of vegetation.

     

    So here's what happened when I attempted to remove a few trees around that tiny airfield.

     

    So as mentioned in a previous post, it's not a precise tool/trick but it could definitely help shaping an area.

     

    Thanks again!

  11. Maybe priming is not final yet.

    AcroGimp from this forum (and a Yak-52 owner and pilot) also noticed that priming the DCS Yak as he would with his airplane end up flooding the engine (iirc he does one shot per 10 degrees below 100°c AOT - so that would be 8 with 20°c AOT).

     

    I also started the Yak with a -10°c AOT mission and 5 shots (cylinders) and 2 shots (pipeline) made it start without any issue. Then warm up cycle @ 51% RPM (by the manual) - also takes ages to get to temp ^_^

  12. I think my only gripe about it, which is more a gripe about DCS visibility, is that the tires marking the airstrips are invisible until you're right on top of them.

     

    We could definitely use better markings for any unprepared airstrip. I wish it'd be easier to add and share (MP-compatible) custom static objects. Then we could use white/yellow stripes and other markings.

    Something that could be added to the very long DCS wishlist, but that would also end up very low in their priority list.

×
×
  • Create New...