@Scorpion82 Yup, same here. It was this one: https://www.scalemates.com/kits/revell-4379-mig-29-a-fulcrum--143832. It had AA-8 missiles and then some that were supposedly AA-10s but which were wildly incorrect.
Latest posts made by Antares
-
RE: MiG 29A Soviet camo
-
RE: F/E/A-18E/F
What do people do when they’ve fired their last HARM? Or do they just keep one for the way back?
-
RE: Test low-poly toys in BMS4..
The second one is a German LARS, right? What’s the third one?
-
RE: Wind Turbines WIP
No I’m not talking about Github as a repository, but more about the Bugtracking it offers. I don’t know if you can’t do one without the other but in worse case we can possibly use some dummy repo or maybe even an active one with Release version data for small fixes which are suitable.
Yes, a dummy repo would be the way to go. Valve, for example, do something similar for their Linux Steam client: https://github.com/ValveSoftware/steam-for-linux. They just have a mostly empty repository containing just a couple of text files, and instead they only use it for tracking issues. I’m pretty sure there are other examples as well.
The downside of that approach is that you wouldn’t be able to take advantage of all the built-in hooks, triggers and actions (e.g. closing an issue when a fix gets merged), but that could be worked around by using custom actions. Lot of effort though, and ultimately icing on the cake.
-
RE: Wind Turbines WIP
I have nothing to do with Falcon4 dev, but I used to be a core dev for the OpenRA project for several years (until my job left me no free time any more ). Anyway, with OpenRA we have made good experiences with using Github to coordinate development of features for third-party mods. Modders would just open an issue that would receive a “feature request” label (or “bug” or whatever as appropriate). We’d discuss what would be necessary to implement the feature, maybe come up with compromises if needed (all within the ticket for all to see), and once the code changes had been merged, the issue would be closed and the third-party modder would know what the state of his request is at any time, and he can plan accordingly.
How does this work for BMS development? How do you keep track of bugs, feature requests, tasks, milestones and so on? Would it be worthwhile to switch to Github/GitLab or similar software? I understand that you can’t upload the source code, of course, but you can just have an empty repository and use only the issue tracking parts of the service. I think that would be much better than keeping track of these things via forums and PMs. I absolutely feel your pain there.