![]() |
|
#1
|
|||
|
|||
![]()
See the thread on Airwarfare.com.
Just out of curiosity, can anybody guess how many lines of code this took? Download Link. |
#2
|
|||
|
|||
![]()
The code is small, so they can't have too many lines
![]() Can we have a look at the whole solution, please? It would be a great help for the other willing modders (including me). |
#3
|
|||
|
|||
![]()
The code for the dynamic mission is compiled within the JG51_Mission.dll. It has about 625 lines of code (without comments).
|
#4
|
|||
|
|||
![]() Quote:
![]() |
#5
|
||||
|
||||
![]()
Just tried the 2 first missions. Getting "you died" no matter what the outcome. Shot down 2 hurries and landed in the second mission. Kills not counted for and status dead.
Does one have to re-play the mission if the status was dead when exiting mission?.... mission 3 was the same as mission 2 for me. Could be that the dead status does this? Also, please move the campaign from main menu to the campaign section?... it's cluttering up the main menu imho. Other than that this has good potential. Great work ![]()
__________________
I7-3930K CPU w/ Corsair H60 liquid cooling. 16Gb Corsair Vengeance 1866mhz. Asus P9X79 Deluxe Motherboard. Asus GTX680 2Gb SLI Auzentech Home theater 3D Soundcard. Corsair HX850 Modular PSU. Win 7 x64 Ultimate TM Warthog HOTAS. TM Cougar MFD's. Saitek Flight Pro pedals. TrackIr 5. Samsung Syncmaster 2770FH LCD. |
#6
|
|||
|
|||
![]()
same happened to me too, get the "You've died message" no matter the mission's outcome, and the 3rd mission is exactly the same a mission 2 (the patrol one against 2 hurris).
|
#7
|
|||
|
|||
![]() Quote:
Raggz, unfortunately that's not possible. The "Campaign" section is reserved for 1C's campaigns. For a variety of reasons, I cannot put my campaign there. If you wish, you can rename my section to something more visually pleasing. Find TEFCampaign.xml in AddIns and change it in there. Adonys, there's really nothing complicated about it. Essentially, it's a glorified text editor, as that's all the mission files are. Most of my time was spent learning how the mission files were actually written. After that, it's just a matter of choosing what type of mission I want to do (there are currently only two for the player), adding some aircraft for that mission, then use whatever remaining aircraft are left to create random missions for aircraft from both sides. Essentially, it's a lot of rand.Next() statements. ![]() If I do release the code, I want to at least comment it all. I also want to rewrite a lot of it. Namely, the code that selects which type of mission to do next. I don't want to release anything that isn't commented and/or sets a bad example. Both things I frequently do. And finally, assuming anybody out there actually enjoys this campaign, what would you like to see added to it? Other types of missions? Ground units? (That would be hard) Oh, and thanks for the log Raggz. It took about five seconds to fix after I saw that. The real question is why did it still work on my computer? ![]() |
![]() |
|
|