DMFS_VC-10_C1K_panel_v1.1 crashes FSX

[willemkelder]

Hallo,

I am trying to install the VC-10 c1k in FSX.
I used the FSX file,s for installing in FSX but when i opened the overhead and try to use a switch FSX crashes after a few seconds.
Did i missed something or is there a other file for FSX.

Hope you can help.

rgds Willem.

[aerofoto - HJG Admin]

The panel is known to be quite stable in FSX..... it "IS" FSX portable.

When you installed this panel (in fact any of the DMFS panels) did you also select and install the 2X panel/gauges components supplied within the "REPLACEMENT FILES FOR FSX" folder which is contained with the main panel folder ?

From memory these are an FSX specific PANEL.CFG and a sound/audio related module.

In order to successfully use the VC10/C1K panel (again any of the DMFS panels in FSX) both of these FSX specific files need to be copied and pasted into the main panel folder among other gauges components .... to overwrite there default FS2004 specific equivalents.

Select "YES/OK" to any/all overwrite prompts.

Not saying this "is" the cause of your issue, but, it may well be .... if you've missed this particular step within the installation instructions ....

Incidentally this particular installation requirement is nothing new to the DMFS panels offered by HJG. It's a requirement which has always been part of the original DMFS panel releases also and for FSX portability


Just one other detail also ....


The current/latest DMFS panels offered by HJG (including those for the VC10 and VC10/C1K .... and all now updated with functional WX Radar sets) are now all "V1.2" and not V1.1. Download links for these specific files (yet to be transferred to our DOWNLOADS section) are provided within the following-linked "New File Releases" announcement of a few days ago (JUN 30 2023) ....
tonymadgehjg.proboards.com/thread/10363/upgraded-files-releases-june-30th

The above-stated "REPLACEMENT FILES FOR FSX" component applied to all of these latest panel versions as well.

Mark C
AKL/NZ

[willemkelder]

Hallo Mark C,

Thanks for the reply,

In the V1.1 version i put the the 2x FSX file,s in the main panel folder.
I downloaded the V1.2 Version and i put the 2x FSX file,s in the main folder.
But i have the same problem like the V1.1 version, so when i open the overhead panel or fuel panel or AP panel or radio panel or electrical panel and i try to make a selection at a switch FSX crashes after a few seconds.
I use windows 11 and FSX.


rgds Willem

[aerofoto - HJG Admin]

You should (really) be using the V1.2 file/s Willem.

The only difference between the V1.1 and current V1.2 files is the implementation of the "functional" WX Radar set .... among the V1.2 release/s.

Beyond this there's no known FSX imposition/s in regard to either of these file versions though .... and none of the recent (since 2021) HJG applied edits/fixes among the DMFS panel series are known to adversely implicate the VC10 OH sub panel or any of the DMFS panels accordingly .... in fact they only successfully promote FSX portability.

I fear the issue, you say, you're experiencing may be located at "your end".

To this extent have you applied any edits or modifications (other than those provided by HJG) to, the panel you're using ?

windows 11 and FSX.

"THIS" (WIN 11) could also possibly be your problem

Mark C
AKL/NZ

[willemkelder]

Hallo Mark,

I found the cause of the problem after comparing the Vickers panel with the Comet panel.
I found the gauge: gauge68=dsd_xml_sound3!dsd_xml_sound3, 2,2,5,5,.\SimObjects\Airplanes\DMFS Shared Files\Vickers VC10 C1K Panel\DM_VC10_sound.ini installed in the [window 00] section.
But in the comet panel this gauge is installed in [Vcockpit01] section and after moving this gauge to the [Vcockpit01] section of the Vickers panel V1.2 and removed it from [window 00] section of the Vickers panel the
problem was cleared and everything works fine again.

Hope this will help you for a update the files.

rgds Willem

[aerofoto - HJG Admin]

The reason those gauges are referenced within the [WINDOW00] position of each PANEL.CFG is because they previously always have been .... as GAUGE # 75 in the original DMFS VC10 PANEL.CFG and gauge # 68 in the original DMFS VC10/C1K PANEL.CFG.

One can verify this oneself should one have access to the both of these original 2008 dated DMFS VC10 panels.

We didn't alter this data (it's [WINDOWxx] location) since there was no reason to do so .... other than to ensure the PANEL.CFG directory line suffix for the said guage read as follows for each of the 2 FS version panels ....


For FS9 VC10
[Window00]
gauge68=dsd_xml_sound3!dsd_xml_sound3, 2,2,5,5,.\Aircraft\DMFS Shared Files\Vickers VC10 C1K Panel\DM_VC10_sound.ini

For FSXVC10/C1K
[Window00]
gauge68=dsd_xml_sound3!dsd_xml_sound3, 2,2,5,5,.\SimObjects\Airplanes\DMFS Shared Files\Vickers VC10 C1K Panel\DM_VC10_sound.ini

For FS9 VC10
[Window00]
gauge75=dsd_xml_sound3!dsd_xml_sound3, 2,2,5,5,.\Aircraft\DMFS Shared Files\Vickers VC10 Panel\DM_VC10_sound.ini

For FSX VC10
[Window00]
gauge75=dsd_xml_sound3!dsd_xml_sound3, 2,2,5,5,.\SimObjects\Airplanes\DMFS Shared Files\Vickers VC10 Panel\DM_VC10_sound.ini


Again our releases have been based on the established DMFS referencing and which did check out OK in FSX during testing .... "according to the feedback I was given here".

But in the comet panel this gauge is installed in [Vcockpit01] section and after moving this gauge to the [Vcockpit01] section of the Vickers panel V1.2

I note you appear confident in having resolved your own issue, but, not sure making adjustments based on comparisons with the COMET panel is ideal.

"Vcockpit" is, I think, a reference to the "VC Panel" supporting the COMET (and both BAC ONE-ELEVEN and TRIDENT VC panels too), but, the VC10 and VC10/C1K are composed of 2D Panels only .... DM never upgraded these simulations with interactive VC panels.

What intrigues me more is I've used both our V1.1 and V1.2 version releases of these files myself (albeit in FS9 .... to generate both the support related and pre-release publicity material here), but, haven't experienced any such issues using these files on both WIN XP and WIN 7 OS's at least .... otherwise I'd have expect any such issues to also materialize in FSX.

I can't speak for WIN 10 and WIN 11 OS's though but it must be born in mind these simulations were never really intended to be run on these later OS's.

I "will" consult in relation to this report and later respond .... but only if there's any need to do so.

Mark C
AKL/NZ

[willemkelder]

Hallo Mark,

Thanks for the info.
I had a likewise problem with the Connies from CalCalsic with the gauge: dsd_fuel_dump!fuel_dump_transparent, 89,443,36,36,.\Gauges\1049_fuel_dump.ini // for FS9 only.
After installation in FSX you have to deactivate this gauge also at the [window 00] otherwise you have the same problem.
But everything works fine so perhaps FSX or windows 10/11 changed something.

rgds Willem.

[aerofoto - HJG Admin]

so perhaps FSX or windows 10/11 changed something

That's possible Willem .... and is precisely what I'm trying to establish now and "before" I make a general endorsement of any findings, alter anything, or replace any files accordingly.

In the meantime I "do not" doubt your experience

The reality is I had 2 people check all of these panels, including both VC10 versions, "IN FSX" during late 2021 and prior to our releasing the V1.1 DMFS panel files. This was done because I don't have/use FSX, so, I'm dependent on that/this feedback.

Neither person whom tested reported any issues.

I "do not" doubt their reports/feedback, but, can't verify which WIN OS's these FSX tests were conducted using.

V1.1 of both VC10 panels is precisely the same as V1.2 .... the only difference being the WX Radar feature now represented in V1.2 of each of the DMFS panel files hosted here.

This new WX Radar feature has no relationship with the said gauge though .... "so far as I'm aware"

I note you've used both V1.1 and V1.2 of these VC10 files .... and with the same results.

Therefore the questions for me, and which I'm now seeking answers to, are .... (1) Are the 2 VC10 panels, with that gauge as it's currently configured, OK in FSX using earlier than WIN 11 OS's .... and (2) Is your reported experience a consequence of using these same panels with WIN 11 .... and which is what I understand you to be using despite the fact these panels weren't actually intended for use with this much more recent OS.

Functionality of the said gauge also needs to be properly analysed too in the event it is ever relocated, so, this's a bit of complex analysis that may take a wee bit of time in order to be able to arrive at a proper conclusion.

Mark C
AKL/NZ

[willemkelder]

Hallo Mark,

Thanks for the info, indeed perhaps win11 is doing something, but this is the solution for the small problem for me and perhaps it will help someone else if they have the same small problem.

This feedback was only for help, and i know FSX is a old so Microsoft will not take care of anything anymore if there is a problem in this Microsoft flightsimulator (money), even the weather function is disabled in FSX, but i think a lot off people still use it.

rgds Willem

[aerofoto - HJG Admin]

I appreciate the way you've handled this enquiry Willem

Just a further comment from me and which may also endorse your WIN 11 suspicions as being the cause of this report ....

The following video was made during late 2021, at the time we were FSX'ing the VC10 and VC10/C1K panels, and also testing new our new RR CONWAY audio for these simulations too ....

www.youtube.com/watch?v=2q6kKYWB83s

The above audio-visual features the V1.1 VC10 panel (the VC10/C1K panel version is similar "compilation-wise") we released during DEC 2021 .... but this makes no difference at all because your report was in relation to the V1.1 as well as the May 2023 released V1.2 panel files and WIN 11.

All I can say with certainty is "FSX" is being used in above audio-visual, but, I don't know which WIN version is supporting the panel/simulation.

As I mentioned above .... 2 people tested both the VC10 and VC10/C1K panel versions in FSX during late 2021 pre-release testing. Neither reported any issues .... and I have to accept the verdict these testers each returned at that time, so again, the subject of this thread may well, as you say, come down to WIN 11 only. At this stage, and assuming this's the case, I see no reason to edit or replace FSX specific data in either of these VC10 panels. If WIN 11 is indeed "proven" to be the cause of your reported issue, then, considering these panels were never intended for use with this WIN version, I may simply opt to post a "KNOWN ISSUES" advisory within the forum based VC10 and VC10/C1K manuals, along with your suggested fix, for people to apply "themselves" .... and again only in regard to "WIN 11 compatibility".

At the moment (given what's known/been previously reported during testing) the panels appear to be fine in FSX .... using up to WIN 7 (and possibly WIN 10 too) at least.

FS2004 is unaffected too .... using up to WIN 7 also (and possibly WIN 10 as well for those whom have managed to get this older FS version running on that WIN platform) .... as I can personally verify through my own use of both panel versions and these simulations.

Again .... "THANKS" for the manner in which you've co-operated/liaised with us so far

Mark C
AKL/NZ

[George Carty - HJG]

I ran the VC-10 panels no problem under FSX and Windows 10 (unfortunately I wasn't able to get FS9 running correctly on my current PC, even though I did on a previous Windows 10 PC), so I believe Willem's problem must be Windows 11 specific.

I wasn't even aware that the VC-10 panels had a [Vcockpit01] section (as these 3D models lack a VC) but it seems like they actually do and that the smoke triggers are there: putting the dsd_xml_sound3 gauge in this section too would seem like a reasonable thing to do if it does indeed fix this problem.

Just thought I'd better advise given that I've done most of the panel work here at HJG...

George

[aerofoto - HJG Admin]

Those are "PRECISELY" the conclusions I've arrived to too George thanks to your help .... a also thanks to Willem KELDER's assistance and whom I've been in contract with.

I'll replace both the VC10 and VC10/C!K panel files ASAP .... and announce when they're available.

Incidentally .... the other day I ran FS9 tests with the DSD XML SOUND3 gauge relocated. It worked fine, so, it seems "IN FS9" this gauge will work perfectly in the original default DMFS location (and which is precisely why we left it as originally supplied) and also equally well in the relocated position too.

Got "A LOT ON" at the moment R/W but expect to have the "adjusted" (rather than corrected) files uploaded "before the end of this week".

"THANKS" George .... "MUCH APPRECIATED"

Like to clarify for folks understanding that only the VC10 and VC10/C1K panels were implicated by this recent report and only in the case of "FSX WITH WINDOWS 11". FS9 was never implicated .... and the HJG/DMFS BAC ONE-ELEVEN, DH COMET, and HS TRIDENT panel files (offered here) were "never" implicated either.

Mark C
AKL/NZ