Luthier?
 

Luthier, is there any chance we might have some input on the bugs in this patch?
How long to fix the tree and shadow LOD?
Are we getting a hotfix for the non starting planes online?
Will the next patch be another beta?
Will we get the hit effects, reflections back?
Will the particles, smoke and clouds be fixed?
Will the AI not able to start their aircraft offline be fixed?
Will the FPS drop for Nvidia 5 series GPU's be fixed?
Are we ever going to see dedicated server files?

Some input on what is happening with COD in the next 6 months, a updated roadmap maybe would be great and since you haven't posted here for 3 months im sure everyone would like to hear from you.

cheers.

got none of your issues. Well I had the tree LoD thing for a short while, but after switching to another tree detail level it is all good now.

*Congratulates myself*

Thats great Redroach, what version of the patch are you running? the rest of us are running this one...

http://forum.1cpublishing.eu/showthread.php?t=32920

Has the problem with the Channel map been fixed so we can use it for co-ops, after all that was the location for the Battle of Britain,
not some fantasy 'cross and roundel' map thats to small to use?

I think that you may be mistaken. Try ‘Free Flight – England’ and turn inland and fly at a height of about 2000 feet. You’ll soon reach the edge of the original tree perimeter drawn when you spawned, and see no more rendered beyond this. You will see the high detail final render if you get close to the ground, but the basic ‘autogen’ trees are missing.

I hope that I’m wrong and you have found a fix, as I’ve spent hours on the sukhoi.ru forums reading Google-translated English, but no-one there has a clue either.

Maybe they want to get rid of real-tree, and this patch is the first phase.. hopeing :-P

:)

Why should I do that? I'm flying the missions I'm interested in and have fun with. Hunting for bugs is one thing and helps to identify low - to - medium - priority bugs, if rare enough, but that's not what I want to do right now. But, if I got time and willpower for that, I might give it a try (while I'm pretty sure it'll work just fine...)

Oh, and I'm running the most recent beta patch, just like anyone else. And after experiencing that bug, I turned down the tree setting from "medium" to "low" - that's still enough trees for me and my hardware. I strongly believe that settings aside from maximum, are there for a reason

*anticipating "ooh" and "aaah" for my tree settings...*

Red, saying you dont have the same bugs because you turned them off doesn't really help does it?
Its like saying you dont have the Hurricane start bug either because you only fly 109s.

Come on please...

Furbs do you always have to try the seriously pathetic attempts at twisting words, low is not off. If this works its better than having a broken lod system, mine is currently set to high and the bug is rather annoying but its a beta.

As always your posts are aimed at poking someone into a response, just act your age and cut it out.

The whole point of beta testing is to find and confirm bugs, but you are definitely not obliged to. If you really have found a fix, there are a many users (myself included) who would be very grateful if you could confirm this. I have tried every suggested fix to date, but none have made any difference whatsoever.

Krupi, My post was asking Luthier for some details on the bugs in this patch, Reds first post said he didn't have any of these issues. If low gets rid of the problem with the trees because the trees are not there it doesn't mean the bug does not exist.
How am i poking anyone?
And stop with the insults.

Krupi, I think you're barking up the wrong Furbs.

Having the same issues. it does eliveate them a bit if i turn down everything but not a whole bunch. here is hoping for another fix soon :)

specs:
CPU: AMD Phenom™II X4 970 Black Edition Quad-Core
CPU Cooling: CoolerMaster V8 CPU Cooler
MEMORY: Corsair 8GB (2GBx4) DDR3/1600MHz Dual Channel
MOTHERBOARD: Asus M4A89TD PRO/USB3 AMD 890FX Chipset
Cross Fire Single Monitor (currently 42in Viewable FP 1920x1080 HD TV)
OS: Windows® 7 Home Premium (64-bit Edition)
VIDEO: AMD Radeon HD 6870 1GB GDDR5 16X PCIe
VIDEO2: AMD Radeon HD 6870 1GB GDDR5 16X PCIe

Again you have missed a very simple point redroach suggested that he had solved the problem by turning the trees to LOW not to OFF, do you not see the difference!


Fixed that for ya.

When is the last time when Luthier posted here?... Please ask yourself? I think some of us set up our expectations way to high with the developers!

PS: Good questions, I would love to see a response!!!...O! one more thing... they usually do no like direct questions!... I think by now we know probably why!

hehe, as I said... I awaited the "aaahs" and the "oohs". Maybe I should repeat it: I set trees to "low". Those are still enough trees for me and the sorrows in this department are gone. Why you are clinging to "high" trees and experiencing problems with that, is your business. Report it, set trees to a setting that is working and save yourself some blood pressure medication and the psychiatrist bills.

And, yes, beta testing: Since I'm not a paid beta tester, I'll test in my own way, if you don't mind. This means that I go online, hop in the plane I want, fly into the direction I want, and shoot up things I fancy. And If I encounter a bug along the way, the first thing is to try to resolve it on my own, instead of immediately going postal in the banana forums; THEN, I'll alert the CoD population, if it's not already done.
As I said, if your way of life consists of pseudo-hubris, by digging, and digging, until you find something, then getting into choleric rage, that's entirely your business.

The sad part of this is that this may actually have hurt CoD in quite a significant way. Some people "tend to" produce major fuss about things like "grass that's too green" and "unrealistic propeller discs". Those issues have lost each and every serious vote in this forums, yet the minority always cried loud enough to get the attention of the devs. Which put us back quit a bit; of that I'm sure.

P.S.: I've had my share of choleric events, too. But still, I believe that I'm able to separate minor issues of major ones.

Hear, hear!

well said

It should be obvious to everyone that the first post in every Friday Update for the past 2 months or so starts with a post of Luthier's that BlackSix puts up under his account.

Either that or BlackSix has intermittent episodes of perfect, witty, vernacular English writing skills for several paragraphs before he relapses into completely different sounding short bits of English that can either mildly or more severely difficult to comprehend. (Sorry BlackSix your English is getting better and I do appreciate your posts). :)

except for the propeller thingy, because that was so horrible, ugly, unrealistic (and headache inducing) it had to be promptly removed/fixed or some people might not even be using the sim for beta testing, let alone trying some game play. point being, for the prop example, this was a newly introduced problem with the previous patch, and was non existent before then, letting that type of new error slip into a long awaited (6 months) beta patch was completely unnecessary and shows poor screening for major new issues prior to that patch release. aside for my own hobby horse there (i was one of the loudest complainants about the prop thingy), i agree with the general gist of the previous poster :)

what isnt happening however, and is leading to a significant amount of frustration (which is then fueled by the small clique of resident perpetual whiners and the newly arrived confused tweens of the me me me generation) is a list of major issues to be fixed in some sort of priority order to improve gameplay in CoD so people can actually start enjoying the sim parts that do work. all we mainly have right now is some basic for of online airquake, and a few very simple missions that dont really show the potential of the sim and what currently does work.

for ex the non-collision tree's fix might still be some way down the line before it can be resolved (better tree collision modeling probably takes a large amount of pc resources which would significantly slow down the sim performance, in the same way dynamic weather would), but it would be relatively simple for luthier's team to fix the coop issue, add some airfield AI activety (which we can set ourselves with some simple controls in the game preferences/options instead of having to go into complex ini script writing), solve some of the reversed control issues in the 109 etc...

it really is a team management issue and the ability (or inability) of the senior people in that group to have an overview and set priorities. luthiers team needs to urgently give some of their time to fix those types of more simple issues rather then keep chasing the perpetual large issues that take much more programing time and manpower, it would reduce complaints on this board by 50% or more for relatively little effort.

another point is that some community involvement is maybe possible to fix some other parts of the sim that do not affect their private intellectual property aspects, and maybe involve some of the experienced modders (some of whom are professional programmers) that are/were involved in the 1946 expansions. might not be simple to choose what to delegate to them (with NDA's), but is worth considering