Anybody know of a good 2D widescreen panel for this bird ?

Thanks

Encountered a Problem. After following the instructions and uninstalling all the 767 models and installing the new 1.5 update base, the 200 version and freighter models will not reinstall. What am I doing wrong?

WOW, this came as a surprise!!

Can't wait to get home and try it out, it's one of the long haulers i fly the most!

Thank you CS! 

I thought the CS 757 4.6 came out quickly, but this was a nice surprise to wake up to.

Looks great Captain Sim!

That came in unexpected for me, great stuff. However, there are some minor problems brought along from v4.6. Wide screen panels must have somehow affected 2D pop-ups, as they're all out of proportion (this is well visible on the CDU, EHSI and EADI). Secondly, I've been looking in the cabs and texture folders, but I can't find what's responsible for drawing regs in VC. It's quality is bad, EI-DDW looked much better. Is there any way to tweak/draw this manually?

As soon as I saw the email I was uninstalling and downloading at the same time

Just what I was hoping for, thank you Captain Sim!

stoked

Great news!!!
CS767 is not LD767, but now we can do a normal flight.

P.D. LOL the forum lost words!

Having weird difficulties with 1.5:  Lost the click spots on the overhead panel in VC mode and can't shut the pilot or first officer windows?!  Would appreciate any advice.

Looks like I'm the only who has problem with this update ?

Here lnav does not work. heading select does not work and when it comes to the lights I can only switch them  off or on using the  "flood" switch. All others do not work either

Mark,


I have done the above but I'm not sure I deleted this Captain_Sim.b767.menu.dll file ? is that supposed to be in the gauges dir ?

Btw, After I installed the 1.5 vs even my 757  started having the same problem.The exact same.

mindyerbeak wrote on Nov 24^th, 2011 at 7:42am:

The Captain_Sim.b767.menu.dll is, as far as I can tell, the same as the old one, it will get reinstalled by version 1.5 anyway (it will be overwritten) so you don't have to remove it if you don't want to. I just do it so I'm getting a clean install IF it gets left behind, which should only happen if FSX is running (file is in use and can't be deleted). I do silly things every now and then, like uninstalling or installing while I'm still using FSX (which I don't recommend). The file can be found in the FSX\Captain_Sim folder, not in the FSX\Captain_Sim\767 folder.

It is interesting to see that this has somehow had an affect on your 757. My 757 v4.6 is still working great. Maybe in this case, you could uninstall them both, then install the 767 and any expansion packs followed by the 757 and any expansion packs, to see if that can sort your problems out. Also. Have you done a computer reboot since you installed the 767 v1.5?

Mark

I have re-downloaded the installers and reinstalled.It's not working at all so no joy!

Is this update anything like the 757 4.5 or 4.6? I ask because I cannot use either of those updates--my flight loses all its settings when I load a saved flight, including IRS alignment, so the plane is unflyable. Has anybody had any such problems with the 767? I don't want to download it if even anyone has experienced such problems.

Thanks!

I wish I had that problem. APU sound is unbelievably loud.

Morten, there is the folllowing entry in "appdata\Roaming\Microsoft\FSX\dll.xml":

	<Launch.Addon>
		<Name>Captain Sim 767 Sound</Name>
		<Disabled>False</Disabled>
		<Path>Captain_Sim\767\cs.sound.dll</Path>
	</Launch.Addon> 

As far as I remember, this entry was not there with version 1400. I only discovered it after the upgrade to 1500.

Maybe this entry is missing in your config?

Regards,
Martin

I have the another company boxed version but have no eds link on the profile page. Any ideas on what to do?

Morten wrote on Nov 26^th, 2011 at 12:37am:


Hi Morten,

good to know that this solved your problem.

Regards,
Martin

mbucholski wrote on Nov 25^th, 2011 at 3:34pm:


Yeah, i wish someone would fix that 

Yeah, i guess i can try that. I have another issue - When the landing gear is coming up, i get a repetitive "windows error sound" while the gear is moving inside the plane and no gear up sound. Any ideas, or anyone getting this?

Reinstalling will do nothing.

Thank you.

CoolP wrote on Nov 26^th, 2011 at 1:37pm:


Wooow, I wasn't aware of that facility..!

Regarding to loudness in general, one should think that there must be a way to put in some other values into one of the cfg/xlm files your self..? Just don't know where and how..
However, from time to time, when I have similar problems I simply take the files an bring loudness up or down in a sound editor, as ex. Audacity!

I had my first actual flight yesterday from Nice to Zürich.
Nice as usual with this wonderful plane, but...hmmm still loads of bugs with sound...some too loud other too low + some annoying "Check landing gear, Check landing gear"!..also some landing light issues and  misplaced wing lights on the VC model, still not corrected with this new version. 

Thanks CoolP,
Moved the value to 21.0 and it got rid of the annoying "check landing gear" and now have no warning sound at any flap configuration ( which is OK). Wondering if there is supposed to be a landing gear warning sound at a certain flap setting, perhaps further down the line than 5% which is where the warning was coming in.  Thanks

You are right, there is a value where the sound is supposed to come up. I would have to look up that exact one though. Flaps 5 is way too soon of course.

The real thing acts as follows.
Landing gear config warning when in flight (gear not extended), flaps in landing position (25 or 30) or any thrust lever idle with a RA of lower than 800ft. The gear override switch then is the only way to prevent the warnings from going off.

The Gear Override Switch itself does the following.
Inhibits the ground proximity TOO LOW GEAR caution.
Inhibits the ground proximity TOO LOW TERRAIN caution.
Inhibits the landing configuration warning siren.

I don't know if all these details are modelled though.   But 21.0 looks like a good setting, so you get your warnings with 25 and 30 again.

The plane flies much better with the 1.5, most noticeable with the A/P. Before it would ascend when it should be descending and just wouldn't follow what was published in FMC. It behaves not perfect, much more accordingly now. Perhaps due to the fact that the A/P in not dependent on the FSUIPC?
With 21.0, I'm not getting any warning sound, even with flaps 25 or 30. With that value, are you getting the warning sound with flaps 25 or greater?

So I put in 20.0 and 20.1 and still no warning sound. With 20.1 I'm not getting any warning sound when I throttle back completely. No problem though. Much nicer not to have those sounds. Hopefully I'll remember to  to deploy the gear before landing. 
Thanks for the links CoolP. I'll check them out.

Trailboss wrote on Nov 28^th, 2011 at 8:12pm:


Be careful with that LOC button, unless you know EXACTLY what you're doing!!
When flying a CAT III ILS Aproach, you only need to hit the APP button at the time retrieving final ILS vectors from ATC, then things will work out successfully.    

Are both 767 gauges entries present in your dll.xml? Can you check if there is a sound for the gear motion in the Captain Sim\767\sound folder?

Should be two.

	<Launch.Addon>
		<Name>Captain Sim 767 Menu</Name>
		<Disabled>False</Disabled>
		<Path>Captain_Sim\Captain_Sim.b767.menu.dll</Path>
	</Launch.Addon>
	<Launch.Addon>
		<Name>Captain Sim 767 Sound</Name>
		<Disabled>False</Disabled>
		<Path>Captain_Sim\767\cs.sound.dll</Path>
	</Launch.Addon> 

Maybe try and report back. 

Those a major issues, but I think something on installing the plane might have failed. Did you try these vital steps? Make that 'to the letter'. www.captainsim.org/yabb2/YaBB.pl?num=1322008495/34#34

To rule out any basic problems, be aware that she needs 'Microsoft® Flight Simulator X SP2 or Flight Simulator X Acceleration.' and that Directx has to be current too. Just stating this because the operation seems to be seriously mixed up.
Does the ACE state some demo mode or something? If so, the protection might prevent some systems from working. Also take a look at your dll.xml and check if those two dlls from the 767 are there.

This is all guesswork of mine though, but please check those items because the issues really look like having a basic nature.

Un fortunatley it didn't work what you said to do, any more suggestions please  or is it a software 'malfunction'?
Thanks.
P.s Does anyone else experience no T/D and T/C on the ND when plotted a flight and does VNAV work because mine doesn't!!

I've had a few issues with some of the switches not responding or don't go to the right place, and the autopilot rocks so much it stalls out the plane. Any ideas?

-Tom

I have tried what you said and unfortunatley, it didn't work, any more suggestions or is it a 'malfunction' in the software?
Thanks.
P.s Is it just me that doesn't get T/D and T/C on the ND and for VNAV to work?

Yes Mark, among many other bugs, this is also happening for me!

Also the LNAV and VNAV randomly cuts off which yesterday caused me a severe plane crash during climb, after sitting for hours manually putting waypoints into the FMS because it suddenly won't accept imported flightplans with the 1.5 version! 

Sys & Equipment manual P40:

18. Speed Knob

...

When VNAV is engaged, pushing the speed knob transfers control of the aircraft speed to the FMS from the speed knob. A subsequent push transfers the speed control from the speed knob to the FMS.
ed.

...

NOT WORKING

Tip: You can adjust VNAV speed within the FMS - VNAV page.

Ciboulette wrote on Dec 4^th, 2011 at 7:09pm:
If you increase the throttle and start moving forward, you can arm the spoilers while still on the ground. They will deploy if you hit the brakes. For a test, try arming them while taxiing, then use the brakes to stop and the spoilers should deploy.

I have heard that the spoilers in FSX are coded in the "Boeing way".
On the AS Airbus X, I think that they created their own xml coding to arm the spoilers prior to takeoff.

Ciboulette wrote on Dec 4^th, 2011 at 7:09pm:
This could explain the "Boeing way".

Mark

Thanks Mark for your profound FSC description - For the time being I'm pretty busy with other stuff. However, I look forward to try out your suggestions as soon as possible!

Markoz wrote on Dec 3^rd, 2011 at 6:44pm:


Doesn't help..!
I'm now returning to the 1.4 version..!

Hi Mark

Just a couple of questions before leaving the 1.5:

1. Have you possibly tried to load FSC8 based plans into your own 1.5 FMS with a successful result? or only FSC9 based plans?
I just wonder if perhaps the CS converter is not able to import FSC8 plans?

2. Another strange thing I noticed, is that it seems that the only 5% of the FSC8 based plans that the 1.5 FMS will accept, is all written in "AceXML" format. Along with these plans there are valid waypoints inside the Legs section of the FMS. Whereas plans written in core text format are completely empty in the Legs section, which obviously is the reason why these plans are non-executable!

I have no idea why the plans is sometimes in this "AceXML" format and sometimes only in text format - however both types of plans format has the same .PLN file extension..!!!
Originally all the the FSC8 plans are made in text format on my client XP PC - but when I transfer the plans to my main W7 PC into the C:\Users\Morten\Documents\Flight Simulator X Files some of these plans (automatically or under influence of CS?) are converted into this "AceXML" format!

Here's an example of a FSC8 based plan LFMNLSZH.PLN that my 1.5 FMS successfully will accept:

<?xml version="1.0" encoding="UTF-8"?>

<SimBase.Document Type="AceXML" version="1,0">
   <Descr>AceXML Document</Descr>
   <FlightPlan.FlightPlan>
       <Title>LFMN to LSZH</Title>
       <FPType>IFR</FPType>
       <RouteType>VOR</RouteType>
       <CruisingAlt>21000</CruisingAlt>
       <DepartureID>LFMN</DepartureID>
       <DepartureLLA>N43° 39' 22.20",E7° 12' 55.80",+000010.00</DepartureLLA>
       <DestinationID>LSZH</DestinationID>
       <DestinationLLA>N47° 27' 29.40",E8° 32' 52.80",+001414.00</DestinationLLA>
       <Descr>LFMN, LSZH</Descr>
       <DeparturePosition>04R</DeparturePosition>
       <DepartureName>Nice/Cote D&apos;Azur</DepartureName>
       <DestinationName>Zurich</DestinationName>
       <AppVersion>
           <AppVersionMajor>10</AppVersionMajor>
           <AppVersionBuild>61472</AppVersionBuild>
       </AppVersion>
       <ATCWaypoint id="LFMN">
           <ATCWaypointType>Airport</ATCWaypointType>
           <WorldPosition>N43° 39' 22.20",E7° 12' 55.80",+000010.00</WorldPosition>
           <ICAO>
               <ICAOIdent>LFMN</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="USANO">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N43° 44' 3.00",E7° 42' 49.80",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>USANO</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="BASIP">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N43° 53' 31.80",E7° 57' 42.00",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>BASIP</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="ABN">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N44° 3' 21.60",E8° 13' 15.60",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>ABN</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="DORAV">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N44° 19' 34.80",E8° 51' 7.80",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>DORAV</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="GEN">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N44° 25' 27.60",E9° 4' 55.20",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>GEN</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="VOG">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N44° 57' 52.20",E8° 58' 12.60",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>VOG</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="SRN">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N45° 38' 45.60",E9° 1' 18.00",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>SRN</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="CANNE">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N46° 10' 0.00",E8° 52' 52.20",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>CANNE</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="KELIP">
           <ATCWaypointType>Intersection</ATCWaypointType>
           <WorldPosition>N46° 57' 22.20",E8° 45' 42.00",+000000.00</WorldPosition>
           <ICAO>
               <ICAORegion>KK</ICAORegion>
               <ICAOIdent>KELIP</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
       <ATCWaypoint id="LSZH">
           <ATCWaypointType>Airport</ATCWaypointType>
           <WorldPosition>N47° 27' 29.40",E8° 32' 52.80",+001414.00</WorldPosition>
           <ICAO>
               <ICAOIdent>LSZH</ICAOIdent>
           </ICAO>
       </ATCWaypoint>
   </FlightPlan.FlightPlan>
</SimBase.Document>
         

CoolP wrote on Dec 11^th, 2011 at 9:42pm:


I could try that - however I'm not sure if the native FSX format will keep my SIDs and STARs extensions added through FSC8..? if not, I can't go that way.

Hi Morten.

I can try it, but it will be a while before I do. FSX decided to go crazy on me last night and now I have to reinstall it. I hate that!

Mark

Morten wrote on Dec 13^th, 2011 at 12:16am:

That is pretty much all I use FSC9 for too, except the moving map. I rarely connect FSC to FSX and track my flights.

Anyway. I'm glad you found a work-around to help you sort this out. It does seem like Captain Sim changed it enough not to recognize the FSC8 Flight Plan (FS9?) format. I actually think it does not have the capability to load a Flight Plan in the older FS9 format and that has a kick-on affect to FSC8 (as explained in my earlier reply).

Mark

You mean the CG entry and the then computed trim setting? I think it stays like on the releases before 1.5, which means that the CG entry already is a bit off from the rw 767 spectrum. You can estimate it in the FSX payload dialogue and then get a FMC trim value.
As that part of the simulation is simplified pretty much, maybe a default trim setting is the most reasonable solution. That's just my impression though.

Markoz wrote on Dec 17^th, 2011 at 6:20am:


Arhhh!..
OK, many thanks for letting med know anyway, so I don't have to risk a fatal crash after all them time-consuming preflight preparations..!!

I'll just ignore the trim settings then and instead use the trim option on my yoke intuitively during climb as I already was getting use to with the 1.4 version - That is, mostly by pressing her smoothly down a bit until reaching the V/LNAV/AP engagement phase at around 1000 agl.   

Another thing, however less important - The weather conditions data via my weather radar is only viewable through the extra HSI popup window and not directly on the HSI itself.

Anyone else having the same problem?

Yeah okay!
I'm trying to use it 100% of the time, but it will only show up on the actual HSI 25% of the time. In fact this error already started back on the 1.4 version - I guess it must be system related, then - Related to my multimonitor setup or my graphic driver.