Jump to content

DonDrapr

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by DonDrapr

  1. Thank you, for the info. I assume - in my case - this has nothing to do with the game build nor my hardware, but is rather a server-side authentification DRM/DLL hickup, not loading certain modules (which are 'free' right now, but I did not buy - hence do not own). Most modules still run flawlessly and performant as before. So far, F-16, F-14 and the Carrier module all don't work for me. Everything else is fine.
  2. I have a 'slim' Win10 SSD just for gaming. "Slim" meaning: only Windows 10 (latest 20H2 stable version) and drivers + VC++ runtimes etc. This 'gaming PC' runs literally over a thousand games (connected via different hard drives/partitions). DCS World OpenBeta has it's own SSD drive. Installed all modules the other day (owned Payware and not-owned promotional access modules). Verified cache. Repaired install. Everything clean and tidy. I played endless hours without issues on this hardware the last year or two (though on the 'stable' branch). The bigger was my surprise why certain modules suddenly don't want to even load. And, I too, get those 'soft' (= silent) CTDs. Is this something rather common on the openbeta branch? My hardware runs the latest RayTracing, VR and other AAA video game titles smoothly and without any problems! Of course, the latest drivers are installed and nothing on my hardware or in my vanilla Windows settings is remotely 'weird' or responsible for these, unique crashes. Very curious to learn, if this is more than 'just a small sample of players'. My hardware is the most common and the hw drivers are mature and make games like Red Dead Redemption 2, Control or Ghost Recon Breakpoint, Death Stranded, etc, etc ... run smooth like butter. But I am NOT curious enough to spend hours hunting down crash logs and helping debug problems. That is not why I own DCS modules. I only switched to the open beta since the latest modules are not available in the 'stable' build (whatever THAT means these days) for more than a year or so. Final point: why 'silent crashes'? Is it too hard to pop a error message box when crashing? That's just not helpful at all, having to hunt and figure out 'what' caused the crash (hardware? OS? GPU driver? ... when it's the game). Bad practice. [AMD Ryzen 7 2700X 16 GB DDR4 3200 SDRAM ASUS ROG STRIX GTX 1060 6GB OC Sandisk 500 SSD MSI PRO Gaming Carbon]
  3. I just encountered this same issue. A workaround is not a patch. It is still there. This is the second training/tutorial mission. It is meant to teach (new!) players, how to operate the aircraft - not how to overcome insufficient programming or vague, casual orders. Every instructor's order for player execution has a keyboard command (/) (F8) ... "... and then switch positions" implies the user already knows how to do that. But s/he was never introduced to 'switching seats'. It is not stated anywhere. The devs just assume every new user knows that keyboard key 1 and 2 are for switching seats/cameras between pilot and copilot. Which obviously is not the case? If you do not switch, instead follow the instructions 'to the letter' (as in "do not press any button until I say so" would be any instructors first rule?!), you are then eventually put in the RIO seat … - with the RIO co-pilot body obstructing your view - no way to toggle the body off - left and right side console instrument panels are missing (no textures) A tutorial should be 'bullet/fool-proof'. The player should not be able to make mistakes or 'fail', or not know what to do next. These are the most basic elements which should 'work' and on top of every bug-list of any kind of sim- and/or game developer, since new users will stop there and not come back. If new users have to googlebing the Internets for a solution, the very first hour in, you failed as a dev? It would be so easy to add to the text: "... switch positions" ('YOU SWITCH POSITIONS BTW PILOT AND CO-PILOT PRESSING (1) and (2) KEY") and then NOT allow the script to do it for you? Then, there would be no actual bug, they could encounter (see "missing side console panel textures" above). Easy to fix? [EDIT] Another "tutorial thing", that is more general and has nothing to do with just the F-14 … Instruction text is fading out. Why? Some instructions are more dense then others, asking (again …) 'new' players to do unfamiliar things - often more then one at a time - in an otherwise 'infinite' time window. "How much RPM did it say...?"; "... to which position should I switch this last button?" Too late. The message is gone. Again: why? There is no real need to fade out the text? Instead leave it on the screen until the player has finished the tasks and pressed 'spacebar'? (Yes, people can press 'pause' or 'active pause' at any time … IF they know about it. But, this is a tutorial. Beginners, remember?) Small things (fixes) make the difference?
  4. I did not play DCS for a while. I do not remember the Axis (Analog) "Horizontal/Vertical Camera View" being blocked from letting users assign it to either left or right XBox ONE/360 Analog Stick. When did that happen? And - more importantly - ... why? There must be a reasoning behind it? Not everyone uses TrackIR or VR day and night, sitting in that "Simulator chair". Using the 'second' analog stick for 'looking around' is a well established 'way' of playing anything. Was there an explanation given? Anyone knows? PS: Please, Forum users, jumping on every thread to amuse yourselves: spare me the "you should use a flightstick/Warthog HOTAS anyway" comments. This is not about you. Due to the "Modifers" I can use 4x12 = 48 different digital inputs PLUS 48 x 3 Analog (2 Axis) Inputs with a XBOX controller... as I do, at times. It's about 'choice' - not what you think other people should do.
  5. Sorry, but this current "arrangement" is completely confusing for new users?! They go to the "Download/DCS World" page and all they see is "2.1 Early Access" and "1.5" ... none of those are explicitly mentioned in this Forum thread - if they even GET to find this forum page (clicking on the News article link). @USSR_Rik talks in his post about "1.5.8 Open Beta" and "2.2.0 Open Alpha" - none of them are on the actual Download page. You are shooting yourselves in the foot here, imho. New, people, who are interested and want to experience what they just saw on YouTube are going to give up, even before their first download? I promoted the 2.5 Teaser Trailer on social media and have to explain now how to 'get the 2.5 version'. That's not how you market your game, successfully. I am not looking for you to explain things to ME, I am telling you, how the most simple things - if not done 'correctly' - hurt badly, what you want to accomplish: new players. New customers.
  6. I would really like to know when the pre-purchase discount is ending, so I can make some December/January wallet planning. I understand, modules are in development, fixed dates are nothing publishers/developers want to talk about, since customers will backfire on them, if they exceed these dates. But knowing until when the discount will last is not a lot to ask? After all, they will release a 'beta' version, not a finished product from one day to the next. I am currently in the buyer paralysis of "Either Mirage now or (Polychop-Sims) Gazelle, if it will be released before February".
  7. Sorry, not to crash this party, but that 'post your specs and framerate' is random and not representative of anything? That's why automated testing was invented and also integrated game analytics tools. Even if you have the same graphics card, different brand with different gpu clock times, gives you different results. Not to speak of OS, OS update version, services running, mainboard chips hardware hell, etc, etc... - so a few hw specs on a forum post says really nothing? Btw, if you want to see what's happening behind the scenes on YOUR hardware, DCS 2.0 shows video debug stats with ctrl + pause (FRAMETIME!), if you didn't know already. The 2.0 also comes with the developers testings tools, if you are REALLY curious. Check the BIN folder and graphics.lua? But use at your own risk. Using pre-recorded scenes and RivaTuner Statistics Server log files or recordings would further dispense the allure illusion of 'testing' something... Of course, this is all just random fun, since the alpha build will be further developed and optimized. There is probably already a new internal build, as I type...
  8. Oh, thanks a lot! I DID catch an (alpha) updater message saying "copying files from OpenBeta" - so they ARE maybe doing some kind of 'smart' update, even though not the terrain assets. All good. [EDIT] Alpha Updater is definitely using files from Open Beta install. All modules are being copied over, before getting patched, for example. THAT was the thing, I was hoping for. No bandwidth wasted. You are a smart bunch, ED devs! :)
  9. Thank you guys, for the response. Does anyone know, if ED gave an explanation why 2.0 is a separate install? Why couldn't they/we just patch the 1.5.x version, instead downloading the same xx Gigabytes of asset files again? I patch Linux kernels for 20 years now on a daily basis. It's not that hard. ;)
  10. QUESTION: DO I HAVE TO UNAUTHORIZE MY MODULES FROM 1.5 BEFORE INSTALLING 2.0??? I am crawling the forums, to find and answer, but the amount is beyond comprehension or reasonable time vs life ratio. People discuss their bandwidth over 10s of pages. If anyone knows, thanks for telling me.
  11. Albatros, NTTR, Spitfire, Mirage ... now Gazelle (VERY impressive first look!)... in the future, F-14A/B, T-2, F-18 ... the Normandy map for WWII - you guys (incl. 3rd party devs/pubs) have NO mercy with my wallet. I cannot keep up, unless I move to DCS World full time. How affordable are those barracks in NTTR Nellis AFB? Is there any house there in "open Beta"?
  12. Is DCS World 1.5 using DirectX Hardware Tessellation for continuous LOD? Background: I made a video zooming the camera out from the airplane. It is still zooming out after 3 minutes! While I moved the camera, I accidently 'hit the ground' and for like a couple hundred milliseconds, I saw a treeline and detailed grass as if either the engine is NOT using LOD at all, or the graphics card is processing the data seemlessly from video memory. I want to accurately 'tag' the video. It is a quite spectacular effect, with no framerate fluctuation.
  13. Thanks, Pilot! Now I need to restrain myself from DDOS'ing that page, by F5'ing like I am Zuckerborg himself.
  14. Somebody tell me a story, so I stop starring at that updater.exe? Btw, is there a reliable source, to find out when the 1.5 is live? ED Twitter? Facebloke? Wall Street Journal Website?
  15. Windows 8.1 upgrade to Windows 10 = all DCS DRM/keys survived without de/re-activation. Win 10 is just like an ordinary kernel patch. Something GNU/Linux does every day... twice. Framerate is great. New Kernel Scheduler is smarter about balancing threads, it seems. Few framerate improvements. Those, not talked about, 'hidden' feature/updates are always worth switching OSes. You won't read about them on any tech website. Even Microsoft engineers are rarely talking about them. Nvidia/Windows drivers are ok. Some Monitor related features are lost (no more downsampling for me. 2nd graphic card (mixed gpu) was disabled by Windows OS - so much for mixed gpu setups). Worked in Win Vista/7/8.1. Maybe a new driver issue. As for DX12 - DX12 'features' are mostly API related and are nothing you/gamers will actually 'see'. It's not like DX8 to DX9 prettier. It's great for developers, if they know how and can dig closer to the metal. Everyone should switch to OpenGL/Vulcan anyway, imo. ExtremeTech had a great article for mainstream users, translating marketing speak to common tongue. Googlebing if you are interested.
×
×
  • Create New...