![]() |
|
IL-2 Sturmovik: Cliffs of Dover Latest instalment in the acclaimed IL-2 Sturmovik series from award-winning developer Maddox Games. |
View Poll Results: i want to know ùore about CloD | |||
i want Ilya to give concrete answers on the future of CloD |
![]() ![]() ![]() ![]() |
89 | 67.94% |
i am happy with the current friday updates |
![]() ![]() ![]() ![]() |
42 | 32.06% |
Voters: 131. You may not vote on this poll |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
||||
|
||||
![]()
It wont make a difference mate,we know that
![]() Cheese |
#2
|
||||
|
||||
![]()
Couldn't vote as i dont think Luthier knows either.
__________________
Furbs, Tree and Falstaff...The COD killers... ![]() |
#3
|
||||
|
||||
![]()
Seems like a really dumb poll
__________________
GigaByteBoard...64bit...FX 4300 3.8, G. Skill sniper 1866 32GB, EVGA GTX 660 ti 3gb, Raptor 64mb cache, Planar 120Hz 2ms, CH controls, Tir5 |
#4
|
|||
|
|||
![]()
The re-working of the "engine" aside, I would like some concrete answers on how many "bugs" (see bugtracker or reported bugs here) they plan on fixing before moving on to BOM. But as others have said...it's a futile request really, I don't think even they know at this point.
|
#5
|
|||
|
|||
![]() |
#6
|
|||
|
|||
![]()
I agree with Furbs, I don't think Luthier can say for sure, or wants to hazard a guess when these bugs will be fixed, or how long the beancounters will let them work before pulling the plug. We know how the community reacts when he guess wrong.
![]()
__________________
Intel core I7 950 @ 3.8 Asus PT6 Motherboard 6 gigs OCZ DDR3 1600 Asus GTX580 Direct CU II 60gigSSD with only Windows7 64bit, Hotas Peripherals, and COD running on it 500gig HD Dual Boot Samsung 32"LG 120hz MSFF2 Joystick Cougar Throttle Saitek Pro Rudder pedals Voice Activation Controls Track IR 5 ProClip |
#7
|
||||
|
||||
![]()
You really don't need an update. The future of the series is exactly the same as we have now and have had for the last five years. We will expend another billion words on the subject and it won't make a lick of difference. This time next year will still be much the same as today. Don't kid yourselves.
|
#8
|
|||
|
|||
![]() Quote:
![]() |
#9
|
|||
|
|||
![]() Quote:
THUMBS UP!
__________________
__________________ Win7, 64bit Ultra Asus P8P67Pro MB Intel i7-2600K Coursair 16GB (4x 4GB), DDR3-1600MHz Gainward Nvidia 580GTX 3GB DDR5 850-Watt Modular Power Supply WIN7 and COD on Gskill SSD 240GB 40" Panasonic LCD TrackIR5 + Thrustmaster Warthog stick, throttle & pedals |
#10
|
|||
|
|||
![]()
I went with the second option, because i don't think it's good to commit to concrete answers when things are uncertain.
They are practically rewriting half the game code with the new graphics engine. In other words, getting done in the span of a few months half of what was done in a few years. I want the sim to be better and trust me, i have my own set of preferred fixes that i think are long overdue. Having said that however, i think that now the best course of action is not to "over-report" for lack of a better word. Much of the gnashing of teeth surrounding this title comes from setting the bar too high and revealing too much early on: when release date rolled around, the half of the stuff that had been implemented was impossible to run on a mid-range PC within the specified system requirements, the other half had been taken for granted and everyone wondered why it wasn't included. I think the best they can do now is keep reporting what gets done. This way expectations can be managed to a realistic extent and everyone knows what the current and next set of aimed fixes are. My only addition, if it were up to me, would be a little more detail. So to sum up, i don't expect a "this time in 4 months from now we'll have this" kind of thing because it's impossible to accurately predict. What i would like to see is something to the tune of "the past week we worked on A,B and C, the first two worked out ok but C is giving us some trouble...we'll keep working on it and add D and E to our job queue for the coming week". Simple, step by step and to the point stuff that everyone can understand and most importantly, with no room for speculation. |
![]() |
|
|