Jump to content

ricktoberfest

Members
  • Posts

    1274
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by ricktoberfest

  1. 3 hours ago, Derbroomaster said:

    No, this is a new map created from another one, just adjusting time of day and unit composition, etc.

    I think you misunderstand me. Try playing any mission on whichever map it is (eg. Caucuses), just enough so that it has to load the textures. Then after a few minutes of that, then try and edit or create a mission on the same map. For me that worked seemingly because the textures had to be “created” by running a mission. 

  2. If you don’t want to learn about anything then you will be limited in what you can do. Most of the time you will either be air to air or air to ground, but not both. If you aren’t happy using the quick missions (I never use instant action) then you will have to learn the basics of the mission editor. 
    Also-  CAS - shooting at ground target enemies currently fighting with friendly ground targets

    CAP - fighting enemy aircraft. 
     

    that’s about as basic as can be done but the whole point of this game over war thunder is the fun in learning all the stuff that you seem to be saying you don’t want to learn 

  3. 14 minutes ago, Derbroomaster said:

    No-go. Waited about 5 minutes or more before starting into the editor. Crashed pretty soon after I opened a map.

    dcs.log-20240417-193628.zip 181.73 kB · 0 downloads

    Have you run a mission on that map recently?  I had the editor causing issues yesterday. I ran a quick start mission from the main menu, then I was able to load into the editor. It’s like the map wasn’t able to load from the editor without having previously run. 

  4. 8 minutes ago, shadowborn said:

    Today's patch change log for the AH-64D says:

    "Game Flight Mode disabled."

    Anyone know what this means? Was it an optional arcade mode that's been removed? If so ... why? Or is it just some pun on making the sim flight model harder? 🙂

    Yes, but it’s not been supported for a long time. Just causes issues and bugs that no one can figure out. I guess they decided to just disable it to prevent those issues. 

    • Like 2
  5. I’m afraid I’m gonna avoid buying this map simply for the fail in splitting it up. Nobody wants this unless they are worried about hard drive space. It makes everything needlessly complicated for creators and users. 

    • Like 8
  6. 2 hours ago, Raven (Elysian Angel) said:

    As it stands I find neither AA method worth using. Mind you, I have an AMD card so I can't use DLAA.
    That being said, I find TAA great for still images but a blurry mess with so much ghosting it's unusable in practice (and it turns close-range bandits invisible).

    I hope the implementation will improve too.
    Meanwhile this is an interesting watch:

     

    I tried TAA but it made all aircraft look like they had canards in a dogfight situation. Just couldn’t handle it. 

  7. 14 hours ago, ACS_Dev said:

    Thanks again to those who answered my questions earlier about this headset. They helped me make the choice on whether to get the Q3 or stick with my Q2. I now have my Q3 and have been messing with it for a couple of hours, so it is perhaps time for me to contribute as well.

    My Setup:
    CPU: Ryzen 5 5600x ~4.3GHz.
    GPU: MSI AMD 6900XT, left as is with no intentional overclock
    Ram: 32gb Trident Z ~3000mhz.
    Motherboard: X470 Gaming plus by MSI
    Cable: Syntech 16ft USB 3.0
    Primary Monitor: 3480x2160 (My DCS profile swaps it to 1920x1080)
    Secondary Monitor: 1920x1080 (Unused for DCS but still being rendered)

    For what it's worth, I got the 6900XT during the great GPU shortage (particularly for the copious VRAM) and I have yet to have issues with it in VR, same for the 5600X. I will be staying with AMD for the foreseeable future.

    Quest 3:
    -90hz @ 4128x2208 (Native)
    -Honzvr perscription lenses
    -APEXINNO silicone interface cover

    Quest 2:
    -90hz @ 3712x1872 (1.0 according to Oculus)

    DCS Settings:

    image.jpeg

    Performance Results vs Quest 2:

    No major difference. My desired FPS is 45 FPS locked without ASW, and so far this setup delivers, both on Caucasus and Syria. Neither the Mi-24, F-16 nor Mi-8 brought it consistently below this. It typically hovered around ~55 FPS when unlocked as I flew around Syria in a Hind on a local-hosted sandbox multiplayer mission.

    Thoughts on the Quest 3:
    Worth it.

    Visuals:

    I am in perhaps the best circumstances for running it at the native resolution as I got my eyes checked the same day I ordered it and the lenses. I can read the F-16 MFDs reliably (except for small text like the bullesye numbers, which is a bit of a challenge.) The switches on the sides are a bit more difficult but are usually still legible. If not, a quick lean to one side solves the issue. My regular office, the front seat of the Hind, was similarly workable. I can clearly read the little charts on the right side with relative ease and the dials are a no-brainer. The CPG's weapon dial is a bit difficult (I can decipher the '30' but not the other letters for the store, for example).

    Something that I really want to emphasize is the edge-to-edge clarity the Q3 offers. I can read the contents of the right F-16 MFD while the headset is directly pointed at the left one. Hell, I can read the Oil Pressure gauge while looking at the left MFD! Interestingly, the edges almost seem clearer, though maybe that's my lenses. Absolutely not happening with the Quest 2. The days of looking directly at a particular switch and zooming in on it are thankfully over.  So are the days of tilting the headset vertically in an awkward and never-ending quest to get the perfect angle on the CRT-looking lenses.

    The Honzvr lenses were themselves a big upgrade from glasses. I have a mismatched prescription but both eyes are in the negatives above -2.5 and I have astigmatism in one eye. Fitting my glasses in the Q2 headset was a big pain and I am very happy I don't have to worry about it anymore. Shipping to me in the central US took 5 days. I also ordered the optics cover for when I am not using the headset, eliminating the problem of dust settling on them.

    The Quest 3's dial for precise IPD adjustment is very handy.

    Comfort:

    I don't use aftermarket straps, the vanilla straps on both were sufficient for me. The Quest 3's do feel a bit more robust. The silicone face cover is a must for me, a greasy sponge being held against my face isn't very fun. My only real complaint with the Q3 is that it's sidepieces go perhaps a further quarter-inch back than the Q2's, complicating  the wearing of my Hyperx Cloud III. I had to angle the pieces a bit up to fit the ear cups over my ears, and it still could be better. This wasn't an issue with the Q2.

    If you are like me and use a wired connection I would strongly recommend that you loop a cable management strap around the strap of the headset and route your cable through that. It reduces the vertical stress on the port substantially and also keeps the cable off the side of your face.

    Note on Privacy:

    Remember that you can used windows defender firewall to block inbound and outbound connections to basically anything, including Quest software, and still use the headset once you have it initially configured. I set my headsets up using my phone's temporary hotspot so Meta never has access to my home's Wifi, disable the firewall rules so it can run updates, and then lock everything down again once I have everything good to go. I can then use it at my leisure for months on end without worrying about the mic and cameras next to me.  I would encourage anyone that strictly uses their headset for DCS to do this.

    Conclusion:

    It was worth the  cost for me. No matter what comes out next, I probably won't upgrade until I rebuild my PC. Even then I may just upscale it instead of buying a new model. It's simply good enough for me, and it would take a lot to make that next step up worth it.

     

     

    Thanks. I have a similar computer setup and was wondering if the 5600x still had what it took. I’m on a rift S currently. Although I’m still waiting, it looks like this might be my next headset

  8. 7 hours ago, =Garuda= said:

    Qcumber,

    Thanks for your advice. I installed Oculus Tray Tool as you mentioned and tried several options including 45Hz forced, but my DCS doesn’t reflect those settings somehow.

    Change the in game FPS to limit it to the lower setting. In my case I limit it to 40 for my rift S

  9. 2 minutes ago, Rockerverb08 said:

    Any recommended engine settings or speeds for cruising with the AI in formation?  I'm trying to stick to keeping the engine nice and cool, but can't seem to get the RPM/Boost settings correct for cruising.

    It should be the same as his other campaign “Blue nosed bastards”. Generally you can cruise at 46” and 2700RPM all day long. Then pull back to the green zones when close in. (I think they’re 35” and 2500 rpm)

    • Like 2
  10. 58 minutes ago, spaceBunny said:

    @baltic_dragon you're welcome. I hope you enjoyed my sarcasm as much as I assume you enjoyed taking my money in exchange for a broken product.

    I'm not sure what makes you think I will get a new version of your broken product with with an engine update. You said the same thing to other people in this thread...

    ...but we've had a "patch" since then and your product is still NOT fixed

    Well, maybe you should un-mark this thread as fixed. Because the issue is NOT fixed. Why not instead wait until "after the next patch" to ensure the issue is fixed before marking this thread as fixed?

    Or, if you have such an issue keeping your products working maybe you should just remove them from the marketplace altogether. I mean, because as it stands, you are knowingly selling a broken product to people which is not exactly ethical. But hey, do whatever you want... obviously.

    You seem to have no idea about how module maintenance on DCS works, and that’s fine. But you don’t need to be an asshole about it.  Do you expect mission designers to play through every single mission every time there is an update to DCS. They must rely on people (nicely) bringing it to their attention, then they can fix it, and then it can be released on ED’s scheduled update timeframe. You were given a way to easily continue on with the mission by simply tuning into a radio frequency and that should have been the end of it on your side, until the next update fixes it for everyone. Buy or don’t buy, but Baltic is one of the best mission creators we have. If you don’t like it, make your own campaigns. 

    • Like 6
  11. The idea of  an A10 operating over enemy territory was never feasible if you are not willing to lose many aircraft. I remember hearing back in the day that the life expectancy of an A10 against the USSR in Europe would be less than 10 minutes in contested airspace. (That’s low altitude tank busting). An Igla hitting even an A10 has a pretty good chance of taking it down, just look at the Su-25 in Ukraine. 
     

    We’ve changed the way we think since the 80’s. Losing 100 A10s to slow down a tank advance is just not on the table anymore. Western aircraft are now built to keep their expensive, well trained pilots, safe. This means unless you’re fighting a 3rd world country, there’s very little place for an CAS only aircraft, and that place can be done with small cheap turboprops. Even in Afghanistan A10s weren’t carrying full loads of bombs and missiles and coming back empty, nor were they operating alone. 
     

    2 A-29s can carry more than enough bombs to provide CAS in such a situation, and F16s, F/A-18s and F35s can be on station faster and take care of whatever needs the ground guys have just as efficiently from 20000’ up now that guided bombs are a regular thing.  It’s all about the training and interoperability. 

    • Like 2
  12. 1 hour ago, jakm75 said:

     

    I would also love to see an aircraft which can see 11Gs (Which is a very stressful spec) and not see the wings atleast damaged...)



     

    There are planes that can pull 11g with no damage, it happened often at the Red Bull air races.  I know that’s not a military aircraft but what I’m saying is that an aircraft can be engineered to withstand it if it is necessary.  It’s more about systems damage, wear and tear, and most importantly human weakness leading to blackout.  
     

    maybe a better DCS metric for avoiding unrealistic G pulls is to have a more realistic  blackout simulation that can’t be turned off in the options. 

  13. Your system is entirely on the brink of obsolescence as far as DCS is concerned. I know because I’ve been there. Your processor and gpu are both very out of date. When I upgraded I did my cpu/motherboard first to an AMD 5600x. FPS did increase but not as much as I expected. Then I went from a vega64 to an RTX6850 and saw a fairly large uptick in my FPS. Now my CPU is the thing holding it back. My son running on the old system (i5 3570k and vega64) can play dcs, but only in light scenarios. 
     

    I’d suggest doing the cpu and motherboard first as that’s the hardest and you can still use your old GPU.   Get 32Gb of ram and any newish I5 or above should do the trick. The more you spend the longer it will still be worthwhile before upgrading again.  Then get a used GPU but not the bottom tier ones. Get either a Nvidia 3060 and above or AMD 6700 and above. 
     

    I’m not one to upgrade every year but even so I’ve put more money into my computer than I’d ever thought I would. Almost entirely for DCS. 
     

    forgot to add: the cpu/motherboard upgrade didn’t increase FPS as much as I hoped but it did make it vastly more stable with less crashing, especially in VR. 

    • Like 1
  14. 12 minutes ago, Qcumber said:

    You set FSR to 0.9. It sets resolution to x0.9 and then upscales to 1.0. 

    Yes, but the upscale FSR looks horrible and I already have good FPS, so I hope and wait for the ability to set FSR at above 1 to get better visuals and less shimmering at the sacrifice of a few FPS which I don’t need anyways. I’m on a Rift S, so every little bit of visual quality helps tremendously as long as my frames stay above 40.   Who knows, maybe it won’t help and I should just put the resolution scaling higher, but above 1.4 I don’t see much difference and the FPS start to drop off. 

  15. 16 minutes ago, NeedzWD40 said:

    If you use the old AI AH-64D as a metric, then about like any other radar. So if you're concerned about being detected, use a quick, narrow scan and don't leave it on all the time.

    I guess I just thought with a low range, the radar is probably tilted below the horizon normally and so might be less visible to RWR than a fighter. Too bad but I guess that’s why the single sweep exists. 

  16. The jet can do most of what it needs for CAS, the problem is the movers and shakers aren’t training the pilots for it. There’s a great article on “the war zone” a few weeks back about this. The US is in serious jeopardy of losing its skilled CAS pilots by not transitioning them to the new planes, and not training new pilots how to do it. It’s a perishable skill and if all the old pilots retire soon and new ones don’t take up the skill then it will have to be relearned the next conflict. Kinda like the Russians with their “carrier” squadrons. No carrier for years means no trained pilots to continue the skills and teach to the next generation of pilots.  

×
×
  • Create New...