Anyone ever seen one of these!

[Worthless]

The unit xxxxxx is to far from the leader ( xxxxxx xxxxx xxxx). The maximum distance for this type of unit is 20,000 meters.

I just completed my first run through of Skylane's latest set of missions for Ceylon. Missions were well done and the AC are all good birds. Had a few hiccups during the install, already communicated to Skylane; all easily resolved. Had a little issue with FrameRates using the Fairey Fulmar, but nothing serious. Very challenging missions. Thanks again go to Skylane.

One little item popped up that neither of us have an answer to. The message above. It appeared in a pop up box when you attempted to access "Advanced Info". The xxxx's represent different ships and locations. This message only occurred when there was a fleet action in a mission. It didn't occur in every mission where a ship was involved, but it never occurred if no ships were in the mission.

In the last mission I had to click through 19 times to clear it. Different ships other than the Hiryu were displayed, some ships took several clicks to clear. None of this interfered with game play. Still it was a curiosity and I wondered if anyone had encountered the same thing before.

The unit JMK_Hiryu is to far from the leader ( Java - Semplak - Buitzenborg). The maximum distance for this type of unit is 20,000 meters.

 

[Blood_Hawk23]

Did you add all of the data for the ships in the descrip.dat and the MDLnames. there was something that will cause issues with the advanced info but for the life of me i can't remember what it is. maybe I'm thinking of the airbase.dat. it has to be something along those lines.

Ohhh... where is the Java - Semplak - Buitzenborg located. are there any stray items in the MB default locations? its just a guess. But, that would put you out side the 20,000m.

 

[Rami]

Reply...

Worthless,

Actually, yes. I have seen that before. It's kind of tough to explain, but the gist of it is that CFS2 likes ships in a convoy to remain close to one another, and when moving ships are set at a distance that exceeds that maximum allowable distance that the sim likes/allows, CFS2 responds with that message in Mission Builder or advanced info.

In MB, it won't even let you save the puppy until you fix it...it can be a royal pain in the arse.

Interestingly, there are two things going on in that description of yours. Not only is there that message, but if you read your post, the "Java - Semplak - Bulitzenbourg" is not the name of a ship, it is the name of an airbase; the ID the mission is using for a ship has already been taken through your airbase IDs. There are ways to fix that though careful hand-editing, but they are complicated and tough to explain.

With regard to the Fulmar, is the aircraft tough on framerates in general? Or, does it just stutter from time to time? If it's the latter, you may want to try putting a couple of hash marks "//" in front of the BBMF Compass gauge in the panel.cfg file for the Fulmar and see if that helps.

 

[skylane]

It is a very strange thing, because the ships in my convoy are close together. After Worthless told me of the problem, I tried the missions again on my computer, because I thought, perhaps the files have become corrupted somehow.
The message does not appear on my computer, the missions run fine as ever. It would be interestingto know, if anyone else has this particular problems when running these missions.

Worthless, did you use the panel for the Fulmar that I uploaded with the missions? I had very low framerates with this airplane until I exchanged the panel. Now it works just fine.

Cheers,

Skylane

 

[Talon]

The best way to do shipformations is the copy and paste method,this way youi don't have to worry about distance from the lead ship.This is explained in the mission builder.The advantages are ships stay in formation and if the and since there is no lead ship no matter what ship is sunk the others will keep moving. Make sur all waypoints are set to "donot evade" I have made Task Forces of 25 ships using this method.

 

[Worthless]

Thanks Rami and BH23......

I expect the "message" quandary is beyond me. Since the mission construction is part of Skylane's package and no-one else has mentioned it, I'd better just let it go. As I said, it doesn't affect gameplay.

Rami

With regard to the Fulmar, there again I'd probably better let well enough alone. The panel I am using is a substitute that came with Skylane's package, and replaces the original in Bruno's BSK_Fulmar. Neither the original nor the replacement panel have a "BBMF Compass gauge", or in any case I couldn't find one. Only a standard "Heading Indicator" shows in the panel.cfg. Anyhow, the issue seems to be sort of off again on again. A stutter certainly describes what occurs near a base but around a bunch of ships and lots of enemy AC it really hits the skids. I made up a test mission with about 16 enemy, and out at sea without a lot of ships it's only an annoyance.

 

[Worthless]

Must be the Fulmar

Curiosity got the best of me and I flew one of the Ceylon missions designed for the Fulmar but at the outset I switched over to the AH Hurricane Mk IIB Trop as the Player AC. None of the problems encountered flying the Fulmar were present, even though my wingman were still Fulmars. Action near the fleet was smooth and numerous enemy AC didn't drop the Player AC performance.

Also, as I approached home base, China Bay, even while the framerates dropped, there was no stutter flying the AH. Performance remained smooth.

 

[Rami]

Reply...

Worthless,

Here is my panel.cfg for the BSK Fulmar, I isolated the gauges with a "//" that were giving me trouble, now there are no more FPS problems with the plane. I was having the same problem with his Spitfires.

// This Panel.cfg file created by CfgEdit
// Built Sunday, March 07, 2010 at 08:12 Build:15090

[Window Titles]
Window00=Fairey Battle -- Main Panel
Window01=THROTTLE_PANEL
Window02=NAVIGATOR
Fixed Window30=%window_title_30%

[VIEWS]
view_forward_WINDOWS=%window_title_00%
VIEW_FORWARD_DIR=1.7, 0.0, 0.0
VIEW_REAR_WINDOWS=30
VIEW_REAR_ZOOM=0.5
VIEW_REAR_EYE=0.0, 0.45,0.50

[Window00]
file_1024=fairey_fulmar_1024.bmp
size_mm=640,480
window_size_ratio=1.00
position=7
visible=1
ident=MAIN_PANEL
sizeable=1
render_3d_window=1
window_size= 1.000, 1.000
window_pos= 0.000, 0.000

gauge00=Hurricane_1!Altimeter, 233,432,48
gauge01=Hurricane_1!Attitude, 292,362,57,58
gauge02=Hurricane_1!Heading_Indicator, 292,427,56,58
gauge03=Hurricane_1!Magneto, 287,306,24,31
gauge04=Hurricane_1!Vertical_Speed, 363,366,50
gauge05=spitfire_mki!Airspeed, 229,365,52,51
gauge06=spitfire_mki!Turn_Indicator, 355,422,65
gauge07=hurricane_1!Fuel, 366,294,47
gauge08=hurricane_1!Clock, 226,293,48,47
gauge09=hurricane_1!Fuel_Selector, 62,416,38,50
gauge10=hurricane_1!Boost_Pressure, 500,429,50,50
gauge11=hurricane_1!Tachometer, 437,362,54,52
gauge12=hurricane_1!Oil_Temperature, 443,417,43,40
gauge13=f4f4_wildcat!Icon-Map, 269,277,12
gauge14=hurricane_1!Gear, 144,351,60
gauge15=hurricane_1!Flaps, 115,391,23
gauge16=hurricane_1!Fuel_Warning, 182,414,20
gauge17=hurricane_1!Starter, 149,435,30
gauge18=hurricane_1!Engine_Temperature, 580,422,40
gauge19=hurricane_1!Fuel_Warning, 323,317,15
//gauge20=DAP_ExhaustFX!ExhaustFX, 0,0,10, ,80
gauge21=concorde!Compass-Display-Toggle, 358,279,10
gauge22=HuntT7_Trim, 10,441,40
gauge23=f4f4_wildcat!Icon-Engine-Controls, 352,291,12

[Window01]
file=Ecu_Background_640.BMP
file_1024=Ecu_Background_640.BMP
size_mm=160
window_size_ratio=1.00
position=6
visible=0
ident=THROTTLE_PANEL
window_size= 0.170, 0.300
window_pos= 0.000, 0.710

gauge00=spitfire_mki!thrust_controls, 1,0,159,191

[Window02]
file=Background.bmp
size_mm=170,170
window_size_ratio=1.00
position=2
visible=0
ident=compass_panel
sizeable=1

gauge00=prop2ERKadf, 85,110,80
gauge01=SPERRY.MARKIII, 2,2,166
gauge02=Mosquito!Direction_Finder, 12,114,46

[Fixed Window30]
file=mirror.bmp
file_1024=mirror.bmp
size_mm=650,540
position=4
visible=0
ident=30
sizeable=1
render_3d_window=1

[Vcockpit01]
Background_color=0,0,0
size_mm=512,512
position=7
visible=0
ident=
pixel_size=512,512
texture=$vcpanel1

gauge00=Hurricane_1!Altimeter, 56,343,107
gauge01=Hurricane_1!Heading_Indicator, 200,340,105
gauge02=hurricane_1!Fuel, 352,53,107
gauge03=hurricane_1!Clock, 63,53,106
gauge04=hurricane_1!Attitude, 192,195,120
gauge05=hurricane_1!Vertical_Speed, 340,201,110
gauge06=hurricane_1!Airspeed, 62,207,108
gauge07=spitfire_mki!Turn_Indicator, 339,336,122
gauge08=hurricane_1!Magneto, 187,83,50,72
gauge09=hurricane_1!Fuel_Warning, 267,110,27,0

[Vcockpit02]
Background_color=0,0,0
size_mm=512,512
position=7
visible=0
ident=
pixel_size=512,512
texture=$vcpanel3

gauge00=hurricane_1!Tachometer, 52,227,132,116
gauge01=hurricane_1!Oil_Temperature, 160,342,100
gauge02=hurricane_1!Boost_Pressure, 293,345,104
gauge03=hurricane_1!Engine_Temperature, 423,336,90
gauge04=hurricane_1!Oil_Pressure, 31,361,60

[Vcockpit03]
Background_color=0,0,0
size_mm=512,512
position=7
visible=0
ident=
pixel_size=512,512
texture=$vcpanel2

gauge00=hurricane_1!Gear, 339,156,135
gauge01=hurricane_1!Flaps, 231,251,50
gauge02=hurricane_1!Fuel_Selector, 78,339,100
gauge03=hurricane_1!Starter, 344,358,60

[Vcockpit04]
Background_color=0,0,0
size_mm=128,128
position=0
visible=0
ident=
window_size= 0.000, 0.000
pixel_size=1024,1024
texture=$vcpanel4

//gauge00=MAPE_P11_COMPASS!Compass, 0,0,128

[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=5050

 

[Worthless]

HUuuuRRAY!!!!!

Slick work Rami. That was just the ticket. Killing those two lines in the Panel.cfg did it for me. I still get a lower framerate around the bases, but it doesn't cause more that a slight stutter. Not worth mentioning. In flight with lots of bogies it kept to about 55 FPS. Smooth as silk. Nice going.

Skylane....Don't know why your panel caused me problems and not you, but all's well that ends well....like they say. Now that I've completed Ceylon on easy. I'll bump it up a notch.

Also, think I'll see if get Buffaloes Over Singapore running in the same install.