Jump to content

fl0w

Members
  • Posts

    810
  • Joined

  • Last visited

Everything posted by fl0w

  1. We're willing to give away our MiG-25RBT work to RAZBAM if they are interested in taking it, but that doesn't ensue a promise of any sort. It's purely up to them to negotiate and make a transaction of a deal for it.
  2. Hey @104th_Money! Thank you for the response. We've decided to open-source the whole guide as a documentation front at Vapour Labs, you can directly view the source code here. The hosted documentation is available here. Please note that it is all a work-in-progress, and we welcome anyone to help collaborate in our Discord server. https://bgsc.rtfd.io/
  3. Hello everyone. It's been a couple of years since I've last made changes to the guide, and there's been some request lately to look into updating it. Currently, we're looking at bringing the guide under the ownership of Vapour Labs, an OSS-based modding team for DCS World. Our eventual goal is to make almost everything modding-related open-sourced for developers to use, and we want to lead that front. In order to meet this goal, we have to consider how to make it easier for modders to contribute to the documentation. There are plenty of things missing in this guide, and it's admittedly very premature - it doesn't do a very good job at explaining some concepts. There's a lot that could be made as digestible content but simply isn't. So, here's some options I'm willing to commit to, based on circumstances: Rewrite our guide as documentation for code tailoring specifically to DCS aircraft modding. (This excludes MOOSE and similar frameworks) If we do this, we'll make a new repository on our GitHub organisation. The tech stack would be reStructuredText, Python and Sphinx. We'll begin looking for volunteers to help collaborate on rewriting crucial aspects of the guide. Rewrite our guide to become more of a "wiki." There are some good places to consider joining this with. I think Hoggit Wiki would be a great place if the staff there are interested in this. Re-create the guide to be a "workouts" example. This would be creating a repository that serves as a DCS mod boilerplate and has examples for numerous Lua devices and techniques. Currently, I'm leaning on option 1 here. I think it's the best route for us to take, and one with the least resistance for keeping open-source possible. Please let me know what you think, this essentially dictates the future of updates to BGSC.
  4. Discord Server Hey friends! I'm quickly launching up a new Discord server for people to join. This is where I will be officially posting more updates and announcements regarding development status; and progress relating to the mod. Please join below! https://discord.gg/xfputaZVyW
  5. You're absolutely right. And, frankly, I want this project to succeed more than anyone else. It upsets me knowing that life takes the upper hand of my time, availability and commitment. That said, I won't let that stop me from achieving what I want. The MiG-25RBT will happen: a community mod by the people, for the people. This is the one thing, despite years of poorly backed up promises in the modding community, that I will absolutely commit myself to making happen. Vapour Labs has currently made what we consider "vaporware" here, and I want to turn that into software. In the next few weeks, there will be a GitHub organisation and set of repositories set up for the project. There's still plenty of work remaining to be done on the MiG, and just to be transparent, almost everything besides the 3D models have been lost due to struggles during COVID-19. But I'm absolutely willing and committed to continuing, even it means I have to start almost from scratch again. I really wasn't a knowledgeable nor good modder years ago, and there's plenty of things I still regret, but I want to make this project not only a redemption to the community but a gift that sets a higher standard. The DCS: MiG-25RBT Mod will happen because the community here is freaking awesome, and I can't lose grip of something that people also want besides myself. Positions will be opening up soon due to the result of COVID-19 eliminating most of my original team backing up the project.
  6. Unfortunately, our personal lives take precedence over our time being able to work on our favorite hobbies or pastime interests. If I am able to recoordinate and resurrect this project, then I will do everything in my power to deliver a promise to the public that this mod will remain in-development. However, I cannot promise that currently. End of the day, I want to make this a thing as much as everyone else. I will try my best to give everyone here a concrete answer within the next few weeks for what I can and can't do. See you all very soon.
  7. We already utilize Discord, and have been using it since the beginning of the MiG-25RBT project in 2017. However, it's an internal "eyes-only" team server that we have since plans were to make a new/separate public one once we had more to go off of but.. yeah. I do actually have a GitHub, you can find it here: https://github.com/goverfl0w. We also have an organization on GitHub but the repositories are kept private (don't want our alpha code being seen by people! :P) that can be found here: https://github.com/vapourlabs. My Discord is fl0w#0001.
  8. Hey guys, I think it's only out of respect now to be complete transparent about what's been going on with the project. My name is Sirius and I am the "Lead Director" which is some title I gave myself 2 years ago working on the project before realizing owner would be better fitting. I supervise all of the development aspects of the Vapour Labs team and what goes on with the MiG-25RBT. There have been a lot of reasons towards why we have been unable to be good at providing information; COVID giving us a belated welcoming gift of making many of us work full-time jobs as well as stressing our communication abilities internally. I want to be the person who makes the apology to the modding community and rest of the DCS community in masse because of this. We all have personal reasons that we can give to explain each and everyone's absence in the project. What's the status of the MiG-25RBT mod? Right now it's in a current state of limbo -- it's not dead but it's not really alive at all either, and that's because the whole team in vogue has been very busy with their own lives and other interests at this time. COVID-19 made us stub our toes on everything since, which subsequently led to having problems with being able to hold internal weekly meetings again, communicating on what's being progressed on and vice versa. Me, myself? Above with all of the other reasons, not even I myself have had the time to make any basic attempt of communicating to the other team members. My public relations person, Cosmic (who I personally trust and had trusted to the time) was the one who posted everything because I was afraid of ever revealing myself. Over time, I began to realize that my fear retroactively affected communication itself to the community. Since 3 years ago joining the modding community and prematurely leaving it, I continued to wear my heart up high on my sleeve, wanting to show that quietly working on something and actually doing it the "right" and proper way would show that I changed. But since, I believe that is all but a little silly except the "don't show something before you can say you have progress" mentality, which I still adopt to this day. How far is the MiG-25RBT in development? I can give a fairly confident answer on this that a lot of the basic systems, e.g. the landing gears, hydraulics, electrical, (+ buses and circuitry components) controls and cockpit have been already coded in their entirety. The development of the mod is broken down into these areas: - Systems Programming - Flight Model Programming - Documentation Translating - Modeling, Animation and Graphics - Testing The team in total used to be around 13 members in size, but because of COVID as mentioned and other interests, it eventually dropped down to 5. We had brought along an aerospace engineer, a very good 3D modeler who used to work for a 3rd party of DCS and native Russian speakers who could give us the most authentic results when we were trying to translate the documentation on flight performance, the engineers manual and a (stupidly censored) pilots manual. I went out of my own way to personally make flights out in Ohio to go see one of the last preserved models of the Foxbat in a museum. What's going to happen to this project? We've honestly heard a lot of feedback and requests for us to take the 3rd party route. I've never been against the idea of the Foxbat being potentially buyable, although I've really liked the idea of having something made by the community; for the community. The reason's for this are pretty simple: 1. I don't feel like I deserve to be a 3rd party developer with my history and skills. 2. We don't have the technical employment requirements to be registered as such by Eagle Dynamics. We have also considered before to do one of two things: 1. Continue the development of our mod independently as the team currently stands, and/or find more members to join our team. 2. Join forces with another modding team. I have not really made a decision on either, but I am sure that I will give more information as time goes on. I would like to thank everyone for the strong support and unwavering commotion to our progress on the development of this mod. It really means so much to everyone on the Vapour Labs team, not just me. I hope to post more soon. If you guys have any questions, concerns or suggestions/feedback, please don't hesitate. We value everyone's words equally here as all we want to do is make a good mod for you.
  9. Hey guys! Due to the recent ED forum engine change, the table has lost its original formatting. Because of this, I spent a small amount of my time to re-format it here. Happy painting! MAP SLOT NAME CHANNEL PURPOSE / FUNCTION DIFFUSE 0 BASE COLOR NORMAL 1 Normals/Depth and Depth Affects (ie Rain/Scratchs on Glass) SPECULAR 2 Surface Properties for Surface Flare Intensity, Width and Reflection (Replaced by RoughMet Map w/ DCS 2.5) DECAL 3 Decal Layer, a opacity layer for adding Decals w/ out changing the base color layer. DIRT 4 Layer used for Dirty Build Up on an Object DAMAGE 5 Layer Used for Procedural Damage Volumetric (Small Scuffs -> Bullet Holes -> Large Holes -> Removed Surfaces) PUDDLES 6 Used to Place Water/Puddles on Surfaces (Puddles on Runways etc) SNOW 7 Used to Place Snow on Surfaces (Snow on Buildings/Bunkers/Runways etc) SELF_ILLUMINATION 8 Used to Make a Texture Self Illuminated (Diffuse = Color, Alpha = Strength) AMBIENT_OCCLUSION 9 Used to Place Ambient Occlusions on Models (Replaced w/ RoughMet Map w/ DCS 2.5) DAMAGE 10 Used to Place Damage Diffuse Color (Appearance of Dirt/Burn Marks around Damage) <UNKNOWN> 11 <UNKNOWN> 12 ROUGHMET 13 Used for Surface Properties, (Ambient Occlusion, Microsurface, Reflectivity) OPACITY 14 Used for Surface Opacity (Mainly for Glass)
  10. Great work guys! Glad to see the recognition.
  11. Hello, everyone! As a quick reminder, users are still able to join our server at this time, receiving temporary direct access to our text channels for the Heatblur Livery Competition. The link is down below: https://discord.gg/kVWcKmN Sirius.
  12. I have a job! Does that count? :(
  13. I'm looking forward to seeing what everybody has to make!
  14. It's been a hot minute since I have ever touched stuff like this. There are 2 problems I believe are coming with this: 1. The Su-25T has no point helper for the 3D model for DCS to recognize the tail hook. 2. If you would like to try and make the tailhook work, you'd likely need to receive the support of FC3 avionics, such as the Su-33, or taking binaries of the F/A-18C. I am not sure if are possible anymore since ED locked them for piracy concerns. Hope that helped! Sirius.
  15. Hello, everyone. We have updated our discord server! A lot of changes have happened, with the contribution of now monthly screenshot competitions, a gallery of livery artwork, and much more. Come check us out! Sirius.
  16. Isn't this my old code from when I was working on the MiG-23UB?
  17. The current Growler mod isn't anything more than a re-skinned F/A-18C the last time I have seen posts about the development of it.
  18. I'd have to argue. I think the only 3rd party with enough VTOL experience to attempt it is RAZBAM, and it's also a rotary aircraft so it would have its own interesting characteristics.
  19. ED could make the best move right now as to not give any release date, which is exactly what they're doing with the Supercarrier because it eliminates any pressure and expectation from the user fanbase. However, users like being updated about the progress of the game, and more so appreciate an idea of when they get their hands on something, so it will always be a tricky pair to balance.
  20. DCS: Livery Art Group An un-official DCS community, established to making liveries. Hello, users of the forums! We are an unofficial DCS community for livery makers of all walks to talk their trade, as well as a platform to connect livery makers with users, doing this is as a hobby or a paid interest, embodied by a strong passion towards doing it. Our existence will remain the same as it originally started: a group of people who share that one thing in common and share their works together. Attached below are links to our various social media pages, which we invite you to follow and join us on. Discord: https://discord.gg/kVWcKmN Forums: https://forums.eagle.ru/showthread.p...28#post4271128 YouTube: https://www.youtube.com/channel/UCVg...aHt4kUuBr_sDEw Instagram: https://instagram.com/livery.art.group Happy reading! - LAG Dictator Team
  21. I recommend referring to BGSC: https://forums.eagle.ru/showthread.php?t=229910
  22. Cobra, what about the JESTER LANTIRN? May we please see a video on it in the upcoming future alongside the Forrestal plans? Even something somewhat WIP would reinstitute the communities' interest in it.
  23. It's PR in general when you hear great things are going to be coming along but things quiet down. I'm certain that the HB developers are working hard behind the curtains to get everything right, at least, I hope so. :D
×
×
  • Create New...