Official Fulqrum Publishing forum - Latest Patch HURRICANES NOT STARTING AGAIN???

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

- IL-2 Sturmovik: Cliffs of Dover (http://forum.fulqrumpublishing.com/forumdisplay.php?f=189)

- - Latest Patch HURRICANES NOT STARTING AGAIN??? (http://forum.fulqrumpublishing.com/showthread.php?t=34626)

Quote:

Originally Posted by MadTommy (Post 465281)

Actually it is the other way around. It only matters what they call it.

But this is tiresome.. clearly you have your own agenda that is not governed by the facts.

Its definitely a waste of my time, when you can't differentiate fact from fiction.

Quote:

Originally Posted by Chivas (Post 465251)

Unbelievable.....If it were the Release Candidate it would be sent to Steam for download. This is still a beta patch of a possible RC path, sent out to the community for testing.

Hi Chivas, I respectfully suggest you look up the definition of "Release Candidate," because you apparently have your terminology mixed up.

Quote:

Originally Posted by LoBiSoMeM (Post 465258)

+1. It's just that.

Now the fanboys can PLEASE tell me if i can start RAF fighters engines?

You have to follow the instructions step by step. Hurricane and Spitfire were well known for having problems with starting the engine. So it's realistic now in this great sim, player have to learn how to use the planes correctly.

Quote:

Originally Posted by Chivas (Post 465267)

Anything could have happened after/if the guy tested the start procedure, the lead programmer may have optimized code in one feature, and that change could have porked another feature. Thats the whole point of releasing another beta patch for the community to test. If they could test everything, they wouldn't bother sending the beta to the community, they'd just send it to Steam when they finished, but we'd be waiting alot longer for the Steam RC.

Chivas. Please stop talking about what you consider to be normal in the software development life cycle. I've been in software testing and QA for 14 years and I can tell you that even from the outside they simply aren't testing this software. They aren't even smoke testing it before firing it out to us. Them telling us it's in beta testing is just lip service and you are just swallowing it, they are buying time but for me that time is just about up.

Quote:

Originally Posted by yobnaf (Post 465333)

its almost 18 month ago i looked in the Readme of the game, what page was it again ?

Don't worry, Luthier will be back on later to answer our questions.

This should be one of them...

How did this slip through the vigorous testing procedure?

Quote:

Originally Posted by adonys (Post 465368)

first of all, re-introducing bugs you've already solved in previous versions shows very, very bad code knowledge, programming or versioning control. most probably all of them.

secondly, they does not look like they weren't testing anything, they were simply not tested anything. they've just thrown together the last version they had on their subversion, and that was it.

as a third point, don't you imagine CoD is a different branch in the code than BoM. Considering they will work together, it is the same base code, which means what we see right now in CoD is exactly the state in which BoM is too. Which is nothing short of disastrous. Their "pace" of fixing things, more than one year and a half after release is almost zero. For God's sake, other companies are making a whole new product, from the scratch, within this period of time. they were not able to just fix some simple things.

I can not see how this might work for BoM, no matter how hard, or from which angle I'm trying to look at it.

At this point, a realistic expectation would be to expect them fixing anything they can at this crawling rate (with many previously working things getting broken) until they'll have to close the business for good, most probably at the time the BoM sale results will come in. And the optimistic one would be to have them release the code, so that we can work on it by ourselves.

As MJ said, this is it!

Quote:

Originally Posted by yobnaf (Post 465333)

Sarcasm?

;)

Will try this:

http://youtu.be/h89GRPFUhaM

Quote:

Originally Posted by LoBiSoMeM (Post 465372)

Will try this:

http://youtu.be/h89GRPFUhaM

Excellent vid Lobi! Not seen that one before. Thanks for posting! :D

Quote:

Originally Posted by ATAG_Dutch (Post 465374)

Excellent vid Lobi! Not seen that one before. Thanks for posting! :D

+1 Great video.

The start up sequence for the Spitfire 1a_100 octane and the 2a are much abbreviated from the video:

1) Throttle open 20%
2). Mixture lever fully back to Auto Rich
3). Prop pitch lever fully forward to Fine
4). Open radiator to 50%
5) Magneto switches on (these will flip on automatically anyway)
6) Fuelcock lever up to Open
7). Press the "I" key on the keyboard to start the engine
8 ) Allow the oil temp to reach 40 C, glycol to 60 C
9) Use this warmup time to adjust gunsight, magnetic & gyrocompasses
10). Hunch down in seat and look unimportant to passing vulchers
11) Tap brakes to release parking brake
12) Apply full throttle slowly, but firmly
13) Use rudder to maintain straight takeoff run
14) Allow tail to come up as you roll using neutral (centered) pressure on stick
15) At 80 mph, rotate and lift off
16) Raise undercarriage
17) Pull prop pitch lever back (coarsen) to reduce rpms to desired level (2600 - 2850 rpms)
18 )Adjust trim to maintain desired airspeed (168 mph IAS)
19) Pull back radiator lever to 50%
20) Adjust trim (never ending job - Spits very unstable in CoD)
21) Monitor temps constantly (oil < 95, glycol < 120)

That's it!