Official Fulqrum Publishing forum

Official Fulqrum Publishing forum (http://forum.fulqrumpublishing.com/index.php)

- Pilot's Lounge (http://forum.fulqrumpublishing.com/forumdisplay.php?f=205)

- - Please explain... (http://forum.fulqrumpublishing.com/showthread.php?t=31314)

ah yeah it was explained, failed internal testing, so some more work to be done on it, what's not clear?? go outside and do something else for a bit, it'll do some of you lot a far bit of good i think. Sheesh

Quote:

go outside and do something else for a bit

I did,it rained,so i went back inside...

Quote:

Originally Posted by the Dutchman (Post 412295)

I did,it rained,so i went back inside...

So did I, it's 0 degrees Celsius outside, wind is blowing and it's snowing, think I'll sit in front of the old PC for a while more.

Quote:

Originally Posted by buddye (Post 412123)

I am also a experience software programmer and manager with over 45 years of experience on major projects (Air traffic Control, Shuttle Flight Software, and BOBII).

After following the COD project for a year, it is clear to me that the COD project has had many basic problems and the type of problems tell me that the programming Staff has turned over (staff coming and going) resulting in major performance, completeness, and quality problems requiring major rework and redesign (the last example being the graphics system).

The past COD Development process is at best inefficient and at worst flawed.

I hope that the significant quality, completeness, and performance problems/issues are all behind us now and the new issues/problems can be fixes correctly and quickly in the future.

Without being a programmer I thought + or - the same since long ago, but I blamed more specifically a bad project management.

I believe that quality must be privileged over schedule, because time passes but s**it remains, and stains badly your image.

Cheers!

Guys its really not that hard to understand.

They have been rewritting massive amounts of code for the sequel and will be patching the sequel code back into CLOD. This has been stated before today many times.

If the original CLOD code was so flawed that this was their best approach, it is bound to have difficult implications for applying the patch to the original CLOD code.

They were optimistic and keen to release the patch and are just as disappointed I am sure. But they are still working on it, and if you dont have the patience, (which is understandable) then go and find something else to do.

I personally havent flown in CLOD for weeks other than testing new Nvidia driver releases. Im sure you all wanted it fixed "yesterday" just like me, but the fact is its not ready and its not worth the pain of releasing it with what I guess they see as a major issue being identified. But they will keep working away at it and I assume we'll get some more updates over the next week.

Quote:

Originally Posted by FS~Phat (Post 412544)

Thank you for your astounding use of logic, some forum members may want to use this post as an example... ahem.

Anyway, imagine the complaining if, after all these months of work, we got a patch with faulty particle effects, crashes, freezing or some other problem. I have complete faith that this forum would look somewhat reminiscent of a lunch time food fight.

I'm pretty sure it would something other food though :)

Keep in mind the absolute sh*tstorm that will occur if they release the beta patch and it runs poorly.

If this patch we've been waiting for for over a year now can't fix the game then I suspect a good number of people here will give up for good on Cliffs of Dover.

I'm sure 1c would prefer people upset about patch delays than people screaming bloody murder because the supposed uber-fix doesn't work.

Well Doggles, I guesss it's like when you need to pee and just wait for it and wait for it (more recoil you know).
If the yellow team would have put out continous small patches people wouldn't expect the one ring to rule them all.

Kudos to them though to keep on rocking.

Quote:

Originally Posted by theOden (Post 412570)

The analogy is a bit distressing... but I think you'll find the smaller patches (fixes) you're whinging about have already been put out - internally, and matched against other smaller patches (fixes), which is where it just might have been discovered that some of the earlier small patches (fixes) have actually been broken by other smaller patches (fixes)... and so the story goes.

much better to have many of the smaller patches (fixes) developed, tested, tested again and again (for consistency) and any tweaks made internally, to the best of the developer's criteria and then run a closed beta just to make sure that all of the combined smaller patches (fixes) actually perform as expected.
In this way, in Beta, some other items may come up which need to have a smaller patch( fix) applied and then tested and tested again and a again, just to make sure nothing else broke in the process.

Then, when the developer feels that after internal and closed Beta testing, that all is performing as expected, they then choose to release a PUBLIC BETA or a RTM PATCH. Hopefully then, in the greater wild, where some people run all sorts of rigs, to all sort of standards and upkeep and integrity... the developer's efforts hopefully will have come to fruit. This of course, is after completely developing, from scratch, a new graphics engine. > SHOCK HORROR < that this may keep you waiting for a while.

better than incessant whinging/ blackmail and silly threats, over every small patch (fix) release