Cobra847

I deleted the reply because I wanted to check something specific before re-posting it and subsequently got ill later in the evening. Nothing nefarious going on except busy developers and getting pulled in many directions. Apologies! Our privacy policy is linked directly from our site, as well as linked from the EULA in the game folder. As mentioned in the other thread, since there seems to be concern about errant http requests, we'll add a new safeguard for ensuring there is no connectivity whatsoever. There's absolutely no aggressive telemetry or malware delivery happening, at all. One of the google fonts was left in the manual which has since been removed (hence it was pulling it from Google) and as noted in the privacy policy, we only have a user counter otherwise. The font-fix should be available in the hotfix, apologies. As noted in the other thread though, our UI will never rely on any online features, so we'll add a fully offline checkbox to inhibit any HTTP requests to inhibit any and all connection requests. As a stop-gap it should work totally fine to just firewall HeatblurUI.exe off entirely. It actually shouldn't; this may be a bug. I will look into it as we want as little CPU overhead as possible since the aircraft itself is very complex. When any UI element is closed, it should be mostly sleeping, and thus use very little CPU resources. We do have to periodically ping some of the UI elements to keep the JS ticking; but it shouldn't incur that much CPU usage.

Hi, thanks for the feedback. I posted in here shortly after this thread was made but wanted to confirm a detail on one of the items and subsequently got sick and didn't circle back. Our privacy policy is linked in the EULA in the game folder, this is the avenue we as module makers for those sorts of things, but I will touch on this subject to link it somewhere more prominently (e.g. the store page). It's also available directly on our website. I agree otherwise, we will add a offline checkbox which should inhibit any http requests for those who do not want any connectivity to happen at all. Note though, that while our UI elements will always be fully usable offline - if we e.g. add baseline functionality to use e.g. Olympus or anything else, it will not obviously not work as these elements will be dependent on connectivity.

Hi! We're currently rendering this at a lower resolution for performance reasons. We are working on some methods to upscale it to 4K without any performance loss, so hopefully in a future patch soon it will be razor sharp at 4k

Hi! We're looking into this, thank you for the report.

As mentioned; we're cognizant of this and these features will only be available in a manner that is secure. The intent is not to provide a general browser experience, but rather serve safe, appropriate content - strictly and safely. Most importantly, everything needed for the module itself runs locally (manual, UI, etc.) without a single byte of data leaving or entering your computer - and so we can even provide further options to further inhibit any traffic for the users who feel at risk by mistakenly hitting a hotkey.

Security is of course important and we take it seriously. Note however that the UI is run and stored locally, using only files stored on your hard drive unless using the specific internet related features.

It's just an example; not something we're noting as being an actual bottleneck right now. The entire module is a product of the whole; and if there's overall more complexity involved, even small things like a few additional vertex transformations every frame can have an impact. Performance is important and while we want to push things onward in fun ways, we're not very enticed into creating unplayable, unfun experiences.

Just to make an addendum to @Zabuzard. Not that our target is the F-14; however the F-4E is definitely far more detailed (30% more code alone!) and runs a higher fidelity and deeper simulation than we've ever done before. I'd also note that the models and art in general are more complex. More things shaking, moving, wobbling means a lot more vertex transformations for your CPU to do. We're working really hard to ensure that performance is reasonable on launch. Currently performance is under the F-14 benchmark, but we've not done final profiling and optimization just yet, so we hope to find more headroom.

what grouchy_creason means is that generally for now we've got our roadmap full and we're capitalized enough to go ahead and execute on that. But it's always an option for a bigger project in the future if we can't swing it without the community's support!

Yes, absolutely! On launch you can use the arg system for this, but later on we will offer all ethnicities- super important for us.

investigating.

The label was sourced from photogrammetry, so it was indeed misplaced in the jet we scanned, thus it's at least accurate to _some_ jets

DCS: F-4E is, as the name implies, an -E. Our -E is modeled mostly after a specific block and set of T.O., however in general, specimens did change slightly here and there. E.g. our cockpit includes the AVTR recorder, which was a later addition to the cockpit across the fleet.

DSCG first with DMAS to follow, indeed.

Soon!

To help alleviate this, you can try forcing your mip bias in the nvidia / amd control panel to a higher value. This will however affect the mip ranges for all textures.

...If you say so.

The issue happens when you have shadows off exclusively because the angle of the light to the glass becomes such to make it appear far more opaque than it is. The flipside of this is that if we tweak this to work well with shadows off- the green glass will be almost invisible with shadows on.

yes, we're aware of this one and will fix it

We have similar ideas.

Correct!

Personally I find the F-4EJ to be one of the coolest aspects of DCS: F-4E! We'll be introducing a Japanese pilot option post-EA release as well

This is an exceptionally unrealistic projection at present. We're getting close. Soon we'll have poured two years of very hard work into the Phantom and thus we're rapidly approaching completion. There will be some gaps between releases as this is something that all parties feel is good, but the development or release schedule on a macro level is not influenced by the 15E. Put simply, and with all due respect, we do our own thing and don't really care much about other third parties. I wouldn't even say we consider other releases quite as competitors, as the rising tide raises all boats in DCS. In the end, our release and development schedule is dictated by quality first and fiscal responsibilities second. Exact release day, seasonal timing or other release deconfliction are a distant third.

The hand is not moving off the stick. EDIT: Also; pedals is an oversight, but our legs move just fine? Am I missing something?

Do you have a bugreport for these? We are not aware of any issues with the navigation system, especially just in the -A at present. Likewise for bombing modes or gun modes. Thanks!