![]() |
|
|
|
#1
|
|||
|
|||
|
Once again I'm facing a stupid bug in the dedicated server environment. If a player uses an existing AI aircraft the AI won't interact with it, this means they don't take-off after the player or they will circle infinitely around the airfield as they don't recognize that it has already taken-off. Very frustrating ...
|
|
#2
|
||||
|
||||
|
From my perspective we need not interact with AI aircraft, but I realise that other people may wish to.
Does my previous post make sense? |
|
#3
|
|||
|
|||
|
Quote:
I'm just tired of those stupid bugs that pop up on every end of this game. |
|
#4
|
|||
|
|||
|
Try contacting naryv via PM if you need help. He answered questions about FMB and scripts at sukhoi and he speaks English. Here is his profile: http://www.sukhoi.ru/forum/member.php?u=1967 Forum interface can be switched to English I think.
He helped Small_Bee with his missions via PM or e-mail. |
|
#5
|
|||
|
|||
|
Quote:
But I'll find a workaround as usual |
|
#6
|
|||
|
|||
|
It's time for a friday update
First the good news. The current build runs quiet well in dedicated server environment. There are some workarounds required (Aircraft selection by mission menu, Autopilot after take-off) because of bugs in the game engine. Hopefully the upcoming patch will fix them. The bad news is that I'm not happy with the overall structure and design of the software (well actually there is none). I don't like the rather static generation of the missions. There is a lot of dead code from the single player mode. Adding new features like radar detection to the current code would be very complicated and ugly. In addition the lack of documentation and the not defined development process makes it hard for interested developers to help the project. So this is not going to work ... I invested the last week to refine the development process, I started defining the requirements and though about a new design of the whole software. A week ago I was close to drop the single player option completely, but my new design has a convenient solution for it. However I must admit, it's not the top priority and will be added at a later stage. The next steps are: Finish to define the requirements, describe the design and start implementing the basic features. Of course this means that there won't be a release in the next weeks. Draft documents: http://code.google.com/p/il2dce/wiki..._Specification http://code.google.com/p/il2dce/wiki...gn_Description If you have some ideas that you'd like to see implement and want to help and take part, please write a "user story" that contains the view of of a user, what he wants and expects and enjoys, much like Osprey did in the post above. I will read it and thinks that I like will be added to the requirements. |
|
#7
|
||||
|
||||
|
Sounds awesome, looking forward to the next iteration.
__________________
|
|
#8
|
|||
|
|||
|
Quote:
Will the new version run as a SP campaign as well? |
![]() |
| Thread Tools | |
| Display Modes | |
|
|