SkateZilla

there are a few things the ED Launcher does better. For me specifically, I use my app to manage all my installs (release and testing, as well as servers). As well as debug / testing purposes (Launching w/ custom arguments / or autoexec settings etc). But I still use ED's launcher for tweaking a few settings sometimes. ED also plans to Expand the launcher, so there's likely a lot of new stuff coming to it. For Example, LUA Parsing of the Options.lua. You can still manage all the App Profiles as before, and launch the launcher, my app will activate the profile, and you can edit within ED's Launcher. I'm not 100% certain i've debugged the LUA Parsing for specific localizations yet, and there's funky behavior when specific values are changed, despite putting version tables for those strings, the LUA Parser sometimes has a stroke. Ie, I sometimes get errors w/ RainDrops Quality, as w/ this latest version, it's now Off, Low, High, instead of On/Off. DCS would auto-set low for anyone that had the option checked prior, so the app tries to do the same, and sometimes it confuses it self.

The app doesn't re-configure windows to use different folders for User Profile, The option is there to point the app to another path for storing the app's data only.

Right now I'm remastering the Wingtanks and 150 Gallon tanks, I have no plans to do antennae or refueling probe. But from what I saw it was also self contained. I May go a similar path, with having a separate F-5E / F-5A Declared, import the base F-5E then declare an sub variant, and add the changes to that variant..

Added to first post. Forgot to mention, there is a online manual, in the help icon on the top right, I'm slowly building the manual sections at a time.

Final Changelog for next public version (sorted oldest items first): Rar File Added to First Post.

Following legal direction does not mean Legal proceedings *(ie Court). As for the above about employees, only RB and the employees know their terms, regardless of revenue amount, in the event the revenue amounts arent disclosed or withheld it's still RB's responsibility to supplement pay. I wont speculate on their contract terms with RB, as it does no good here.

That's assuming the obligation to pay the developers is ED's to begin with. ED pays RB, RB pays his employees. if ED doesn't pay RB, it's still RB's job to pay his employees. Does the pepsi delivery guy go after walmart for payment when pepsi doesnt pay him? nope. ED executed their contract breach procedures as directed by their legal team for RB breaching their contract. If ED pays RB the contract terms, then there would be no reason for RB to continue trying to resolve the contract breach as they would still be getting paid therefore nothing urging them to resolve the issue. Paying RB during the negotiations doesn't bring the modules back, they never left, apart from the F-15E Radar Time code integrated by the Radar developer, the modules are all fully functioning.

By default in the current Stable build, If FC3 is installed and Authorized, it disables the individual aircraft. It has been this way since the beginning.

Why would anyone disclose financial operations and account status regarding one company's revenue, to someone that's not part of either company.

The community is hilarious, No News/Announcements wasn't well received, So ED started tentatively announcing things, and then whenever there is a delay, people say to just stop announcing things. it's like going full circle. Does someone wanna go through the last year of patch announcements and count how many were delayed, bet it's under 10%. I've seen the Post by Chizh that leads one to believe this, and I'm pretty sure everyone is missing context and mis-interpreting his post,

Default ones are in: \DCS World\Config\MonitorSetup\1Camera.lua You should make a Custom profile in: \Saved Games\DCS.<branch>\Config\MonitorSetup\ Rename it to something like 1Camera-VR+Screens.lua then change the name in the LUA as well. Edit the height/width Values to match you total display area, Or, Paste into notepad++, edit what you need, then save into the Saved Games\DCS.<branch>\Config\MonitorSetup\ Folder, Launch DCS, Check the "Mirror Use DCS Resolution", then Choose this monitor Profile, Relaunch DCS.: _ = function(p) return p; end; name = _('VR+MFDS'); Description = 'Left/Right on the monitor, Mainviewport in VR Headset' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } LEFT_MFCD = { x = <pixel position of left edge of MFD>; y = <pixel position of top edge of MFD>; width = <pixel width resolution of MFD>; height = <pixel height resolution of MFD>; } RIGHT_MFCD = { x = <pixel position of left edge of MFD>; y = <pixel position of top edge of MFD>; width = <pixel width resolution of MFD>; height = <pixel height resolution of MFD>; } VR_allow_MFD_out_of_HMD = true UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center

You can export MFD's to Separate screens in VR By: A. Adding "VR_allow_MFD_out_of_HMD = true" to monitors.lua B. Checking the box saying "Use DCS System Resolution" in the VR settings in DCS C. Set System Resolution the Correct resolution (ie, same res you would have if you were running 2D. C. Setting the Coordinates for the MFD Windows.

Just a quick blurbl, The Wintip tanks are undergoing a re-master pass, -Revamped and re-shaped the 3D Model. (the shape was adjusted, and re-smoothed, some parts were re-built). -Revamped the UVW Coordinate Mapping. (I actually re-did the unwrapping twice, because the first pass had some issues.) -Merged all textures into a single texture file. (Glass, body, illumination etc are all one single 4096 Base texture). -Converted to use the latest PBR Elements. (Glass, Chrome, Metals, Oil, AO, etc) -Revamped template w/ more detail / stencils. ( A LOT MORE! ) -Oh, And Let there be Light. *(Tweaked to be minimal in the day, but visible at night) Once the PTB 50 Tanks are done, I will start on 125 Gallon 2 and 3 Wing Tanks as well as Formation Light Equipped wing tanks. -Wing tanks will have standard and Formation light equipped versions in the loadout, unfortunately I haven't found a way to link weapon animations to model animation state, so the standard will have lighting always on *(WIP Images below), and the Formation equipped versions will have formation lights always on. *(If I find a way to pass the aircraft argument state from the aircraft to the weapon and able to use that to set the weapon arguments I will integrate such function. * pretty sure it's possible, but I just haven't gone down the LUA rabbit hole of Getting aircraft states and passing it to an externally attached model. Like prev. versions, this will be a self contained object mod, dropped into SG Folder, and the user simply add's the loadout lines to the core F-5E LUA. T-38 Community Mod compatibility is not yet determined, it will depend on whether or not the T-38A has wingtip pylons to attach items.

Resolution = Viewport Window Size, Minus UI windows that are docked. The issue your seeing is even with 4X MSAA Set in the options, there's still a lot of jaggies,

My Apologies, when the caffeine wears off I ramble.. Feel free to cleanse my posts to avoid public confusion.

Well, For starters, no one said "court", they said "Legal Proceedings", which has many paths for businesses, But, if ED takes RB to court it would be in Switzerland, as that's where ED's office is located, and if they are the one's filing the suit, it would be held in their jurisdictional facility / system. if RB takes ED to court, it would be in whichever jurisdiction RB's company is registered in and the court system they file claims in. It would be RB Team / RB Legal team and ED Team / ED legal team, and 99% of these hearings are done via Video Conferencing, it's not like ED or RB have to fly out to somewhere remote and physically sit in a room with the judge. As for "Winning", in business cases, it's not about "Winning" it's about legal declaration of whether or not the party's claims are valid, if so, the outcome would be decided by the contract terms or business laws for that jurisdiction. Two companies with legal claims/disputes often settle out of court through legal mediation before going to legal litigation. Regardless of the the path, Legal teams often advise their clients to not make public statements about the situation, as they can/will often be used in the meetings.

Not to get technical, But the actual state of the A-29 likely isn't the seed. *( 3D Model, FM, Systems etc., or even if any production work had been done at all ) If I go to another party *(Say BoBo Studios LLC [It's a rando name]) and I say I will give them DCS: F-15E Source Code for a 24 Pack of Dr. Pepper, Once both parties agree, then it's a breach of RB IP as I used the RB IP in exchange for something of value. It wouldn't matter if it was Monetary, Physical Items, or Digital Items. *(I.E. Data/Manuals for Said Aircraft). Once something has been agreed on, and the deal is made, it's done. Bigger companies are facing similar issues *(which is why I keep saying it's not just a ED<->RB thing), this is par for the course, You aren't a big studio until you face at least one of these legal hurdles. *( Bungie is still under investigation for Destiny, as MS is saying they took IP that belonged to MS when they left HALO development. How long ago was destiny released?, you get my point. MS is still under investigation from several Aircraft manufacturers from the original FS2020 Lineup, it's now 2024, and they were notified during the FS2020 Beta which was in 2019, and they are still selling FS2020 with those aircraft still in their sim.) Right now consumers are for the lack of a better term, Stuck in the Middle. They have no say in the outcome, they have no information other than what's been made public, so it's hard to show trust in either party. So the tree, at least for me, is basically I'm not blaming anyone, it's a contractual dispute, let it be resolved so we can get back to and keep enjoying the Aircraft (and not Just the F-15E, all of them), regardless of what information is public, and my position, I'm still a consumer as well, and I'm not taking any sides/camps or protecting this company over that company, there's no point to backing anyone, as it has no bearing on the legal proceedings, and all it does is promote segregation within the community *(ED backers vs RB backers), Ironically, none of the backers have any information that prove either camp is right. Yes, ED withheld payments due to what they stated to be an IP breach, it's not illegal, and done by every company at one point or another.), That's literally the only thing that's been confirmed. Everything else is heresy. *(belief or opinion). RB : I feel for them, working several months without being paid, its tough. I've been through similar things with other studio paths. ( I waited a year to get paid for some scenes I rendered ). I've also had ad revenue and donations with held for several months, for wearing a T-Shirt w/ a logo on it during a live stream. ED: I understand as a business, they have the right to protect their IP. Like I said, consumers are stuck in the middle, it's like being 5 yrs old and Mom and Dad are arguing about money, being 5 yrs old, we don't have a clue what they are talking about.

Ima tell you right now, despite what you've read on the "Exposed" Reddit, Screenshotting discord messages that are made in heat of the moment during conversation, and then used w/o context to push a narrative for views. You do not know the reason for the delay, and there's no point speculating about it, it had ZERO to do with the current situation, no one was p'd off or pitch forking or pointing fingers at ED over the delay. This is the narrative websites that have a habit of posting egregious stories and claims wanted to push.

Cause that article is posted by a reputable source, on a reputable page... As far as Delays, there was delays, but they were not related to this issue.

I've seen plenty of talk by both camps supporters, both sides get pretty opinion driven on the discord. I'm sorry, you are grossly mistaken. The F-15E Release was prolly one of the more smooth releases. In terms of Functionality etc. Nothing needs to be said by either party until it's resolved one way or another, There are no "Weekly updates" in legal proceedings. The sooner everyone understands that and stops reading into rumors, comments and such on discord, regardless of the direction they go or who they support, The better off everyone will be during the legal proceedings.

Time Bombs Execute code at a specific value for date/time. This is not a TB. The Radar framework isn't executing any code to disable the radar, all radar modes are simply not processed, A2A, A2G, RALT, Etc etc.

How can people still be replying to this thread with the same AV Authorization problem assuming it's RB modules breaking over this?, Like read the 1st post already. It's borderline intentional kool aid stirring at this point.

In the case of the F-15E, the Radar systems Library makes several function calls to Environment.System.GetSystemTimeAsFileTime

Pretty sure ED said old completed modules would be maintained in the state they were in, nothing new added etc.

You're Mis-representing my statement, When Ron said they choose not to participate in Sales, that was in reference to the Spring, Summer, Winter, Fall, XXXXX Holiday, Massive Discount Sales. That screen grab is not fake, as I've seen the discord conversation in question and it's actually several weeks old now, as the issue with the M2000C was already fixed. That being said, the victimizing is relentless, the subcontractors and employees have no say in having items pulled from sale, the contract terms control that, until the dispute is resolved, nothing changes, that much has been made abundantly clear. RB removed the links and plastered their site with messages re-directing everyone to E.D, the dispute is a 2-Sided legal conflict, RB is trying to push everyone to believing it's 100% on E.D., when it's not. Whether that was RB's intention or not really doesn't matter at this point because the outcome is clear, there are 100s of deadplayer servers w/ the "#PayRazbam / BoycottED slogans, there are comments being left all over ED's YT and FB Pages, Negative reviews on DCS's Store pages, and not ONE, A SINGLE POST, asking RB to do anything. By going public w/ something that should have remained confidential, RB has basically put the community against ED, whether that was intentional or not is regardless, *(though posts on discord from the subcontractors nudge in the direction of, it was). People believe everything on social media and discord, mainly due to the lack of information. Consumers will have to wait until the legal proceedings are concluded for any type of information and resolution. RB Employees posting on discord is only making an already drawn out process longer for several reasons.