As usual, I'm now at the wrong end of the garden path and the shovel is in the shed...
hr = SimConnect_SubscribeToSystemEvent(hSimConnect, EVENT_SOUND_STATE, "Sound");
What I have done is to create a read/write routine that writes additional information to the saved flight .fxml file. This additional data contains the full state of the aircraft at that point. Once the FLIGHT_LOADED signal is received via SimConnect, the .fxml read/write routine loads the...
If you go that route, the replacement bitmaps must be the same size and colour depth. Some resource hackers can deal with mismatched information but you're better off assuming that the one you are using cannot do this.
Rob: that's extracted from Doug's code. I've been talking to him recently and he admits that he's lost interest in flight simulation. He was good enough to pass some of his source code across and of course, there's a lot more available on his website still. I did a skim-read of the xml sound...
Hmmm. I rewire motorcycles for a hobby and I can spot an overheated wire of any colour at ten paces.
[Edit] It seems that white was just popular amongst manufacturers, but a shedload of aircraft now have multicoloured wiring looms.
Well, we already knew that.
...but then I work in Belfast and have, at one point, worked in Short Bros. That was the first time I ever came across a Lear 35 in build - white spaghetti hanging down everywhere. I've always wondered why avionics wiring is always white.
Now, Ed will probably tell me I'm wrong :D but I've found you need to MarshalAs on a per string basis
Public adf_ident As String
Public adf_name As String...