Operation Seelöwe

[+GKABS]

Outstanding details and great job I congratulate you Gepard.  

 

[Wilches]

Man, I made a ride over London and what a experience!!!! There´s no parallel in this game! Simply awesome!!! It´s the first time in SF serie that I overflew a large city and the best - with very high FPS. I confess I was afraid of that. The airfields are unique and perfect. The map is useful until DDAY as there was no frontline  change. I´m very much impressed with the work and I imagine how hard it was. Congratulations Gepard!!!!!!!!!!

[Gatling20]

This terrain is outstanding, great job, thanks Gepard. 

[+Gepard]

I'm working on a minor update.

First: correcting the typo in folder Groundobjects, which must be Groundobject.

Second: tactical numbers for the tanks, beginning with the german vehicles:

Third: i try to mod the missionscontrol.ini file in a way, that the Hurricanes does not crash a half squadron while takeoff. Me-109 and Spitfire does not have this problem. Dont know why.

[NIELS]

Simply stunning!........................Bravo Gepard....Bravo!

[+Gepard]

On 25.5.2021 at 9:48 PM, Gepard said:

Third: i try to mod the missionscontrol.ini file in a way, that the Hurricanes does not crash a half squadron while takeoff. Me-109 and Spitfire does not have this problem. Dont know why.

The problem has nothing to do with missioncontrol.ini file.

A quick and dirty solution would be to open the data.ini of the Hurricane scroll down to the chapter: [Engine]

look for line

AltitudeTableData=0.896,0.935,1.000,0.982,0.965,0.740,0.623,0.355,0.000,0.000000

and chance it into:

AltitudeTableData=1.000,1.000,1.000,0.982,0.965,0.740,0.623,0.355,0.000,0.000000

It is not perfect, but it helps, that the losses during mass takeoff become much less.

[Wrench]

I did it slightly differently -- mind you, this is at best an inelegant solution, and at worse a hack

this is for the Huricane Mk.1A, by Raven

BACKUP YOU DATA INI FIRST!!!

here's the =FlightControl= Section, with different numbers

[FlightControl]
StallSpeed=42.19
CruiseSpeed=114.0
ClimbSpeed=90.66
CornerSpeed=125.170
MaxG=5.00
MaxSpeedSL=162.0
MachLimit=0.60
PitchDamper=0.5
RollDamper=0.125
YawDamper=0.1
GunBoresightAngle=0
RocketBoresightAngle=-0.1

Then, down in the engine section, I raised the horsepower

SLPowerDry=990000.00

TK MK.9 spit uses 1113479.3 for it's "dry" HP (non wep). As the Hurricane didn't have WEP ... and only 1000-ish HP....

anyway, it's a hack but it stops the mass crashes. Climb speed is still around 105-100 knts (indicated), at 42% power -- which I still think is too low, but it better.

 

 

 

 

[Gatling20]

I don't want to hijack Gepard's thread about this great terrain, but I think the problem is in the Raven flight model TakeOffRotationAngle, which is way too high for a WW2 prop aircraft (15-20 is for most jets).

[AIData]
TakeOffRotationAngle=20.0  <--  make this 8.0 to 10.0, and I don't see any prangs on takeoff

 

Making the engine power 990000 (which is about 1325 hp) will just make the Hurricane an uber-plane in combat.

[Gatling20]

Squadron (16 aircraft)  takeoff from RAF Debden, August 1940:

 

[Wrench]

and what about everyone else wibbly-wobbly-ing around the sky? watch flights 2, 3,4, and you'll see what I mean. also, use the f6 view, and you can see they airspeed numbers

like i said in my post, "at worst, it's a hack". you don't have to use it

[+Gepard]

A question: Is someone interested in a mod of BoB2 terrain with focus on Operation Overlord?

To simulate the allied invasion it would be neccessary to rework a major part of northern France and to implement a network for strategic nodes for a campaign.

[Wilches]

I do!!!!!

[+allenjb42]

Yes please. Think you can have it ready for June 6th? 

[+Gepard]

53 minutes ago, allenjb42 said:

 Think you can have it ready for June 6th? 

Sure. But not this year.

[dsawan]

This is nice. Anyone know of menu screens to go wit the scenery and maybe campaigns centering on overlord, operation sealion or battle of britain?

[+Gepard]

6 hours ago, dsawan said:

This is nice. Anyone know of menu screens to go wit the scenery and maybe campaigns centering on overlord, operation sealion or battle of britain?

A campaign with focus on Operation Sealion (Seelöwe) is part of the download of Battle of Britain 2 terrain. For Overlord the terrain does not fit yet, because there are to less target areas and possible strategic nodes in the Normandie.

[Gatling20]

I'm loving the detail of this new terrain. Here are some screenshots of Veltro2k's new He-111H on a mission from Evreux Fliegehorst to London:

This crew might have to get used to Canadian rations for a while.

Edited June 5, 2021 by Gatling20

[+Gepard]

Will be part of the minor update: British Cruiser Mk.1 with tactical letter code

Would be nice if we would have a correct Cruiser Mk.I tank, instead the LT-35 placeholder.

 

[+Gepard]

Gatling20 made a new skin for the Cruiser Mk.1 placeholder, so that it now looks more british.

[+JulioJunqueira]

Hi Gepard
The airfield of Wissant works normally on single missions but in campaign mode the airfield show up as RAF base. 
Any clues to fix this will be wellcome. 

 

Edited June 7, 2021 by JulioJunqueira

[+Gepard]

I dont know why it happens. Theoretically all is correct. The base is set for the german side, the frontline is correct. Sometimes this happens, but one or two missions later the base is blue again.

[Wrench]

commando raids???

seeing the 111 screenshots above, I can't help but hear Ron Goodwin's score from the move!!

[+Menrva]

12 hours ago, Gepard said:

I dont know why it happens. Theoretically all is correct. The base is set for the german side, the frontline is correct. Sometimes this happens, but one or two missions later the base is blue again.

You have to double check the frontline data. Frontline coordinates must cover the entirety of the terrain, they must go from 0 to 1000000 (or whichever the maximum size of the terrain is). If you don't divide the terrain exactly into two parts via frontline coordinates, this may happen. It's the only plausible reason (unless that area is involved in ground war strategic nodes), I've had same issues while making the new ODS campaign, until I fixed the front line data. You can specify a different front line for each campaign you create, so no need to change the one of the terrain's movement.ini file.

Edited June 8, 2021 by Menrva

[Wilches]

DDAY +1!!!

[+Gepard]

5 hours ago, Menrva said:

You have to double check the frontline data. Frontline coordinates must cover the entirety of the terrain, they must go from 0 to 1000000 (or whichever the maximum size of the terrain is). If you don't divide the terrain exactly into two parts via frontline coordinates, this may happen. It's the only plausible reason (unless that area is involved in ground war strategic nodes), I've had same issues while making the new ODS campaign, until I fixed the front line data. You can specify a different front line for each campaign you create, so no need to change the one of the terrain's movement.ini file.

 

The frontline starts at 0.0 and ends at 1200000.0. It covers the complete width of the terrain

[FrontLine]
Position[001]=0.0,433000.0
Position[002]=709000.0,529000.0
Position[003]=761000.0,567000.0
Position[004]=763000.0,577000.0
Position[005]=769000.0,583000.0
Position[006]=787000.0,583000.0
Position[007]=791000.0,581000.0
Position[008]=803000.0,583000.0
Position[009]=805000.0,589000.0
Position[010]=807000.0,591000.0
Position[011]=813000.0,593000.0
Position[012]=851000.0,611000.0
Position[013]=887000.0,619000.0
Position[014]=993000.0,714000.0
Position[015]=1200000.0,979000.0
StartShow=2
EndShow=14