|
VCs
Feb 27, 2007 7:02:13 GMT -5
Post by dalecaruso on Feb 27, 2007 7:02:13 GMT -5
An open question ... do any of our members ... or are aircraft designers usually good about positivly responded to requests to nix the VC ... whose instruction for presenting such are contained in the .model file (if I am not mistaken) The reason is that, while most are great, it totally @#%$'s up the operation of my CRAPPY Dell 2350. The sound call schrills and buzzes at a defining level (came with the GeForce2 MXMX 400) and I am tried of trowing money into to the SUB-STANDARD Machine. I cringe when looking from side to side.. even in 2d mode (which works fine) when the side views are from the VS, let alone cycle through the VC to get to the Spot plane view.
Dale
|
|
|
VCs
Feb 27, 2007 8:42:05 GMT -5
Post by windrunner on Feb 27, 2007 8:42:05 GMT -5
Dale, the only way is to "erase" the vc from the mdl is with a hex editor; wich can be a nightmare if you don't know wxactly wich string to touch...altermativetly, you can try to modify the panel cfg by erasing all the lines containing the title [VCockpit]; this won't erase your Vc but its gauges only, and this (hopeflully) may help you with some added fps.
|
|
|
VCs
Feb 27, 2007 9:10:31 GMT -5
Post by dalecaruso on Feb 27, 2007 9:10:31 GMT -5
I have had moderate success with that method .. erasing the VC references in the Panel config. For example.. with the C-54 ... the problem aircraft (NOT that the aircraft is anything short of great.... but with MY computer .. ) I like the panel and use it as the panel of choice with the DC-6 and because the file is different, the VC without functioning instruments appears (works fine) .. going to modify the panel config on the DC-4 panel .. see if that eases the problem Dale
|
|
|
VCs
Feb 27, 2007 9:42:13 GMT -5
Post by Dave3cu on Feb 27, 2007 9:42:13 GMT -5
Dale, A little OT, but have you considered the problem might be a driver issue? I at one time had the Geforce2 MX400 64mb PCI in my HP (as an UPGRADE ;D ) and didn't have any problems, except fps of course. The best driver set I found was 53.03. Anything above that pretty much trashed the graphics, though I don't recall ever having your audio problem. The other possibility would be audio drivers. Dave Edit: I see windrunners suggestion has given you some success so this message may have now become academic.
|
|
Deleted
Deleted Member
Posts: 0
|
VCs
Feb 27, 2007 11:09:23 GMT -5
Post by Deleted on Feb 27, 2007 11:09:23 GMT -5
Dale, here's my 'standard' reply to this that I've used elsewhere.... As far as removing the VC from the A/C model is concerned, it is perfectly possible and actually quite simple to do, involving only a hex editor and one change to the aircraft.mdl file. Open the mdl file you want to edit and search for the following hex value: 0022003900 In the SECOND occurrence of that string, simply change the 39 in 0022003900 to 00. It should now look like this: 0022000000. Save the changes, OK the creation of the backup file then exit the editor to test it out in MSFS. Method: Open the .mdl file, hit Ctrl+F and enter 0022003900 in the "Find" box. To eliminate the vc, you must change the 39 in the SECOND occurrence of this string to 00. NOTE: Since this same string appears several times in the file, you must be careful to alter the correct string. For example, in the DC-3.mdl, altering the FIRST string only loses the plane's shadow, so leave this string intact and hit "Find next". Changing the 39 to 00 in the SECOND string loses the vc. Do not change all the strings 0022003900. Because then you would make not only the VC invisible, but also the landing lights and even the plane itself, so make only the change to the string that handles the VC. It has been determined that only the second occurrence of the 0022003900 string concerns the virtual cockpit, the first occurrence switches off the A/C shadows. A good hex editor can be found here (Hex Workshop 4.1 - shareware but fully functional for long enough to get the job done and then some): www.bpsoft.com/downloads/
|
|
|
VCs
Feb 27, 2007 11:56:07 GMT -5
Post by dalecaruso on Feb 27, 2007 11:56:07 GMT -5
I will explore that method ... Dave ... is the "53.03" driver set available at the GeMax site .. if so I will give that a go first. That might also address some graphics issues that seem to accompany the Audio problem.
Dale
|
|
|
VCs
Feb 27, 2007 12:02:01 GMT -5
Post by Dave3cu on Feb 27, 2007 12:02:01 GMT -5
Yes, their available here Dale: Windows XP/2000 Driver Archive. For different OS you can backtrack from there (Download Drivers). The 53.03 drivers are for a graphics 'card'. If your is an 'integrated' chip set it may require different drivers. Also, when installing new drivers, it is advisable to clean out the old drivers. Driver Cleaner Pro 1.5-Free-at Softpedia does the job nicely. Print out the 'readme.txt' and follow the instructions. Dave
|
|
|
VCs
Feb 27, 2007 13:26:57 GMT -5
Post by dalecaruso on Feb 27, 2007 13:26:57 GMT -5
Mine is intergrated ... and not reading the WHOLE post ... LOL... but thanks to the AOL security center ... did a Sys restore from a point last night. However, something (both before and after) screwed up FLightsim and I can't get it to start ... SO... its "Happy, Happy Joy, joy" Re-install flightsim time. BUT unlike times before ... I will remember to protect the stuff I have accumulated by re-naming the current program file Then after installing ... drag and drop in the stuff I want to use again. Then it's on Plan Z ... modifying the .mdl files. Dale
|
|
|
VCs
Feb 27, 2007 14:23:57 GMT -5
Post by Dave3cu on Feb 27, 2007 14:23:57 GMT -5
Maybe 'my bad' Dale,
Dell specs for the Dell (Demension) 2350 indicated that video is the integrated Intel 845GL chipset. No mention they made that model with the NForce/GF2 chip set.
I added the comment concerning card vs integrated as an after-thought. Might have been after you read the post.
Dave
|
|
|
VCs
Feb 27, 2007 14:59:50 GMT -5
Post by dalecaruso on Feb 27, 2007 14:59:50 GMT -5
No ... the video card was upgraded and replace - from Dell ... so am using that card. Their intergrated card was pathetic.
Dale
|
|
|
VCs
Feb 27, 2007 18:56:35 GMT -5
Post by dalecaruso on Feb 27, 2007 18:56:35 GMT -5
Rollerball .... Downloaded the Hex Editor and followed your and the program's instructions ... LOVE it when things work as "advertised" ... THANKS so much for the assist.
Dale
|
|
|
VCs
Feb 28, 2007 3:25:02 GMT -5
Post by windrunner on Feb 28, 2007 3:25:02 GMT -5
Good to see you're having success Dale!
This is a question for roller: are those values the same for every plane? I'd like to create some "lighter" planes that have VCs for AI traffic without them.
|
|
|
VCs
Feb 28, 2007 5:51:12 GMT -5
Post by dalecaruso on Feb 28, 2007 5:51:12 GMT -5
I just finished using it on the C-54 .. and the DC6s .. both models. it was the same. going to give it a shot on at least a couple of more ... the one great this is that it also creates a .mdl back up of the original.
Dale
|
|
Deleted
Deleted Member
Posts: 0
|
VCs
Feb 28, 2007 14:52:13 GMT -5
Post by Deleted on Feb 28, 2007 14:52:13 GMT -5
Glad you had success Dale. It wasn't my info originally - just something I picked up along the way - I just hung onto it because it's come in handy a lot of times. Yep windrunner, it's the same code for all aircraft if they have a VC in the first place. I'm not sure that it helps for AI though. When I suggested it would do someone said it doesn't make any difference - may even have been here on TOH can't remember. I still like to think it does though
|
|
|
VCs
Feb 28, 2007 19:10:16 GMT -5
Post by Admin on Feb 28, 2007 19:10:16 GMT -5
It actually doesn't remove the VC, it removes the VC view. It's still there (check mdl size before and after) you just can see it anymore.
|
|