|
Author
|
Topic: Problems with .9 Mission Editor
|
Wing Chaps Pilot
|
posted 09-08- 09:19 AM
I've installed the new patch first in a subdirectory in SDOE, then into the main directory when the following problem developed.I can fly just fine in .9, and I can get it's benefits, like the OpenGL rendering and higher resolutions. I can get night missions someone else has created. I can do missions (create them) in the old mission editor, but when I try to create them in the NEW missions editor, I can go all the way until I hit 'save', then it crashes telling me that it performed an illegal operation. I can even load a scenario, but I can't save one. Ideas? V/R, Chaps IP: Logged |
Wing Chaps Pilot
|
posted 09-08- 05:42 PM
The error message is...MISSIONEDITOR caused an invalid page fault in module MISSIONEDITOR.EXE at 0187:004229a7. Registers: EAX=0100ffff CS=0187 EIP=004229a7 EFLGS=00010206 EBX=00000073 SS=018f ESP=0070f5b8 EBP=0070f80c ECX=0100ffff DS=018f ESI=7ffffffe FS=0c5f EDX=7fffffff ES=018f EDI=00456ecc GS=0000 Bytes at CS:EIP: 80 38 00 74 03 40 eb f1 2b c1 e9 8f 01 00 00 c7 Stack dump: 00456ecd 0045b8d8 00000000 0070f6dc 00400000 bff7e265 00400000 bff7e1d2 00400000 0070f690 0070f6dc 000000ff 017a0198 0070f690 bff8098b 00000409 IP: Logged |
Nat JAG
|
posted 09-08- 07:55 PM
I get exactly the same problem Wing, never been solved yet (every patch version after 1.51), no-one seems to know why it happens, don't suppose your a Voodoo user aswell are you?IP: Logged |
Wing Chaps Pilot
|
posted 09-08- 09:27 PM
No, NAT, I'm nVidia Geforce 256. Actually, that probably led directly to me being here, since Red Baron 3D is no good with nVidia.At least that worked out well. It's killing me, though, because I'm anticipating that Zeppelin L-9, and I'd like to be able to write night missions! What to do, what to do! V/R, Chaps IP: Logged |
Nat JAG
|
posted 09-08- 10:55 PM
You can manualy edit the mission files, ie build them in the stock mission ed, and then add the colors and settings you want, beware - this takes practice, here's an example of a night mission setting:msnWindDirection 0 msnClearColor 0 0 0 msnFogColor 0 0 31 msnLighting 0.100 0.100 ) msnSquadron OK, so how do you do it? Like this, in the above, the beginning and end parts you will find in all missions, so I've copied them to help show where the color settings are placed. msnClearColor is the sky color, here set to black if memory serves, but the numbers 0 0 0 are RGB color numbers, so, you can use a paint prog to make a color, check it's RGB number, and replace the 0 0 0 with your numbers eg 255 43 89 msnFogColor is the same RGB setting, but this is for the Fog, fog color should be set close to the clear color or it can look odd. msnLighting controls abient lighting and model shading, changes to this should be very small, as small changes make big differences. I suggest you copy what I pasted above, and then open a mission and paste that into it to see what it does, then change the values a little so that you can see the changes. When saving the mission again, makesure that you don't accidentaly save it with the txt extension or else it wont show up. Good Luck! ~Nat~ IP: Logged |
Jeeves JAG
|
posted 09-09- 01:15 AM
I have tested it and it seems that if you use a user-created squadron (like one from Nations....), it will cause a CTD...switch to the default squads, and it seems to work fine.Note the word SEEMS....it really has only been me testing it....I talked with Werner about it and he has others testing my theory....I am not sure whether it is the patch's fault or not...but in all other regards, Nations is fine. You can go into Notepad and change manually the squad names and it all works out fine. IP: Logged |
Wing Chaps Pilot
|
posted 09-09- 05:58 AM
Great, thank you both!I'll check both... either way is workable... I can either copy the settings from a scenario who's colors I like (open it up with a word editor, copy and paste) or change the squadron names later. V/R, Chaps IP: Logged | |