Dusty Rhodes Posted May 2, 2009 Posted May 2, 2009 The point is they should be coding DCS A-10C or maybe they are too far into that, then they should be coding DCS ??? to Multithread, use all a CPU' s cores, and for SLI/Crossfire. Don't do it now, and maybe not with A-10, but anything after that should have all issue's addressed. Dusty Rhodes Play HARD, Play FAIR, Play TO WIN Win 7 Professional 64 Bit / Intel i7 4790 Devils Canyon, 4.0 GIG /ASUS Maximus VII Formula Motherboard/ ASUS GTX 1080 8 GB/ 32 Gigs of RAM / Thrustmaster HOTAS Warthog / TrackIR 5 / 2 Cougar MFD's / Saitek Combat Pedals/ DSD Button Box FLT-1
EtherealN Posted May 2, 2009 Posted May 2, 2009 (edited) The point I'm making is that making, say, AH64A (if that is the third module) address all of those things will most likely push back it's release date massively. The jobs they have at the moment are: - 64bit, to allow larger and more detailed scenarios and maps. Moderate job. - Move some physics to GPU's that support it. Moderate to big job. - Change the engine to be multithreaded. MASSIVE job. It's only after those that I expect the GPU's to become a bottleneck. Trying to do them all plus SLI-support in once go will push release dates very far into the future and I'd much rather they plan things in such a way that they have a chance of keeping the planned 9-month schedule rather than bumping it up to several years between each. I suspect it will all be done when they are in a position where they can deploy an entirely new engine, since converting an existing and large codebase to multithreading can be more difficult than having multithreading in mind when building a new engine from scratch. But I don't want the third module to be postponed just because the new stuff isn't in yet. Far better to just continue using the good (but limited) stuff they already have and give it incremental improvements as time allows and then introduce the big changes When They Are Done™. End point: I think you don't fully appreciate exactly how complex it is to multithread an application - and especially to modify an existing codebase to become multithreaded. It's not exactly like you just flip a flag in your compiler. EDIT: Here's an anandtech quote: Implementing a multithreaded system requires two to three times the development and testing effort of implementing a comparable non-multithreaded system, so it's vital that developers focus on self-contained systems that offer the highest effort-to-reward ratio. Admittedly an old article. http://www.anandtech.com/cpuchipsets/showdoc.aspx?i=2377&p=3 Edited May 2, 2009 by EtherealN [sIGPIC][/sIGPIC] Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules | | | Life of a Game Tester
GGTharos Posted May 2, 2009 Posted May 2, 2009 The point is that you shouldn't be telling the devs what it is they 'should' be doing. They inherently know far better than you do, they can prioritize better, and they have a plan. And something about there being many clones. The point is they should be coding DCS A-10C or maybe they are too far into that, then they should be coding DCS ??? to Multithread, use all a CPU' s cores, and for SLI/Crossfire. Don't do it now, and maybe not with A-10, but anything after that should have all issue's addressed. [sIGPIC][/sIGPIC] Reminder: SAM = Speed Bump :D I used to play flight sims like you, but then I took a slammer to the knee - Yoda
Dusty Rhodes Posted May 2, 2009 Posted May 2, 2009 (edited) GG, DO NOT tell me what to say and what not to say unless I am breaking the rules of the forum. I have worked with ED and know how they priortize things, unless it has changed drastically, they don't prioritize very well. I would like to say though that it seems things are different because of the excellent shape that BS is in. (I think you can thank Matt Wagner for that.) I am meerly saying what I think should happen and if you don't like it, say so, but DO NOT tell me what I can't say, unless there is a rules violation in what I said. Edited May 2, 2009 by Dusty Rhodes Dusty Rhodes Play HARD, Play FAIR, Play TO WIN Win 7 Professional 64 Bit / Intel i7 4790 Devils Canyon, 4.0 GIG /ASUS Maximus VII Formula Motherboard/ ASUS GTX 1080 8 GB/ 32 Gigs of RAM / Thrustmaster HOTAS Warthog / TrackIR 5 / 2 Cougar MFD's / Saitek Combat Pedals/ DSD Button Box FLT-1
EtherealN Posted May 2, 2009 Posted May 2, 2009 Well, the devs know the codebase they have to work with intimately. You don't. So telling them what they should do (rather than telling them what you would like to have) isn't really appropriate. Though that can be semantic nit-picking, sure. [sIGPIC][/sIGPIC] Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules | | | Life of a Game Tester
Nedum Posted May 2, 2009 Posted May 2, 2009 I don't think the graphics are to that level as of yet, a single card is more than sufficient. I would suspect with future DCS modules (not for at least 3 years imo) would implement better hardware support in terms of multi CPU's / GPU's. At the moment a single GPU does the job. Thats not true! CPU: AMD Ryzen 9800X3D, System-RAM: 64 GB DDR5, GPU: nVidia 5090, Monitor: LG 38" 3840*1600, VR-HMD: Pimax Crystal/Super, OS: Windows 11 Pro, HD: 2*2TB and 1*4 TB (DCS) Samsung M.2 SSD HOTAS Throttle: TM Warthog Throttle with TM F16 Grip, Orion2 Throttle with F15EX II Grip with Finger Lifts HOTAS Sticks: Moza FFB A9 Base with TM F16 Stick, FSSB R3 Base with TM F16 Stick Rudder: WinWing Orion Metal
Airway Posted May 2, 2009 Posted May 2, 2009 Sorry, but it is true. I don't bother to say simulations in general, so Black Shark too, are CPU dependent, more than GPU. Simulation improve more from a CPU upgrade than from a GPU upgrade. My 2 Pfennig
Duke49th Posted May 2, 2009 Posted May 2, 2009 (edited) I just want to quote the Tom Peterson, Marketing Director of Nvidia: SLI is not designed for gamers. Gamers should use a newer single card(gpu) insead of SLI, Triple SLI or quad SLIIt was written in a german paper. It is not the original term. But I can't find the article right now. The article was about the SLI microfreezes. And by the way, a sinlge card/gpu does the job! The ATI 4850/Nvidia GTX 260 is really enough to play in 1600x1200 @ high details. Except you want 32xAA & 48xAF lol Edited May 2, 2009 by Duke49th [sIGPIC][/sIGPIC] 49th Black Diamonds - DCS & Falcon BMS Online Squad
EtherealN Posted May 2, 2009 Posted May 2, 2009 Actually, you don't even need a 260. My 9800 (of a model that appears to no longer be sold) plays it in 1680x1050 at maxed out graphics and 16x on AF and AA without breaking a sweat. (Though I have lowered those since the AA was causing flickering on some buttons.) [sIGPIC][/sIGPIC] Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules | | | Life of a Game Tester
SuDepp Posted May 2, 2009 Posted May 2, 2009 ..beneath... ME/ switched from 8800GT to 260GTX last week.... - NO FPS GAIN AT ALL WITHIN DCS:BS! - Greets & peace to all :love: S@uDepp // Hasi @4,5 GHz @ H100i // Asrock Z87M Extreme 4 // Avirex 4x4GB // PALIT 1070 GTX SuperJetStream // Corsair 350D // Plextor extern // DELL 2407WFP // Razer Lancehead // 2xThrustmaster T.16000M + Saitek Pedals Pro // Oculus Rift // 3x amBX // Win10 Pro x64
Recommended Posts