hughlb

The whole “it wouldn’t be fun because you fly from point A to point B, drop an LGB and return home” is an opinion totally at odds to what many of us enjoy about flight simulation. The entire civ sim community is born out of a love of flying straight and level. Do we have to enjoy air Quake to enjoy DCS? Really? Because that’s not what gets me strapped in every flight. Microprose F-117 was my favourite flight game from my childhood because it was about avoiding conflict not engaging in it, because you knew you were in trouble if you didn’t hide. Like a good thriller, it was all suspense. We also have multirole, air combat and ground pounding really well represented, whereas the F-117 would be a new experience. I really hope it gets a full fidelity module some day.

Surely with the 15, 17, 21 and 23 represented, the next logical step is the 25. Like the Viggen, I really enjoy it when DCS brings an unusual aircraft into full fidelity module. The F-14 really opened up otherwise unrepresented long range BVR combat, which is fascinating. The 25 would give us something we couldn’t just turn fight in, and instead use different tactics and immense speed/altitude to defeat threats. It’d be a unique experience.

Confirm this is happening for me with the latest open beta (F-14). Can a community rep give us an indication of the status on this problem?

I'm holding on too tight. I've lost the edge.

The Hornet is seriously intimidating in a knife fight.

This is it! And now the bending of truth to my employer on the week of the 13th begins...

Winter 2019 - Which means, between now and March 22 - that news has been available for several months.

Cabzi, we have known about those solutions for some time now. That doesn’t resolve the issue, because the issue is related to an interaction between frame rate and the refresh rate of the TrackIR camera. A lot of your settings improve the problem when combined with a stable frame rate of 60 or 120, which is not possible to maintain perfectly - thus, stutter.

I'll chime in I pursued this issue in 2016 - https://forums.eagle.ru/showthread.php?t=174828 https://forums.naturalpoint.com/viewtopic.php?t=13991 I have opened tickets with ED and NaturalPoint, both of which ended up with one side pointing the finger at the other, or in the case of NaturalPoint, throwing it in the too hard basket. After many months of independent testing, I strangely (not really) arrived at the same conclusion as Goa (and others). In fact, reading this thread for the first time today, made me chuckle, somewhat painfully, as we are all clearly in the same boat. The problem is repeatable, the "fixes" are the same, and now with more people buying fast monitors, we are getting more discussion. I will say this though - despite the problem being repeatable in all TrackIR games, it seems to align itself with how a given game integrates their view system, in that I get a similar but different stutter depending on the game. DCS has had similar issues with its mouse look functionality, also stuttering in the past. I can't help feel that despite the 120hz sensor limitation, its also about how ED are integrating it. Perhaps we can seek some clarification in this thread about the future prospects of resolving this issue. I mean, I don't see 60hz monitors as being the norm for simmers down the line, and vsync may very well have its day. I would imagine if we are vocal enough, we can at least get this on the radar.

As the title suggests, I just reinstalled Windows, whilst keeping all my apps and data. I have “full screen” disabled in game, as it reduces stutter when I manually alt+enter into full screen. However, I tried alt+entering and the screen just blinked for a split second, and didn’t seem to activate full screen. Normally it sort of switches on and off with a satisfying double blink, but this is now consistently different. Has anyone experienced anything similar? I have tried reinstalling the display drivers through DDU but it doesn’t resolve the issue.

I’m getting a frame rate drop from capped 60fps to 12fps, yes 12fps, as soon as I get within a certain altitude of the ground, a few hundred metres. If I pop up above that height my frame rate goes straight back to 60fps. It’s isolated to this map, and only is rectified by dropping my view distance to medium or low. What is odd is that my system seems more than capable of holding 60fps, and neither my GPU usage or CPU usage is hitting the limits. It seemed like a VRAM issue, but I’m only using 6 out of 11 GB. Perhaps it’s a terrain object LOD issue? But then I would expect more people reporting it. I have dialed down ground clutter, shadows, AA etc and they make no difference. I’m not running vsync. It’s odd that it drops so much and so precisely.

If you are coming from a 1080p 24-28 inch monitor, and moving straight to VR, then VR is going to be practically life changing. But the same can be said when moving to a 34 inch ultrawide or 42 inch 4K. That experience is as immersive, with the exception of objects in the immediate vicinity like the cockpit, trees, or buildings. I have tried switching to my Rift multiple times, usually after reading threads like this. But I keep feeling underwhelmed by it - it's not bad, even the resolution isn't a deal breaker, it's just not as enjoyable as my monitor - I can sit for hours, I can see my home cockpit switches, the extra screen width gives me great situational awareness, and it looks really nice. In fact, aside from it not being a true 3D environment, I find canyon flying to be as thrilling on a big monitor as in VR. One thing I simply can't recapture on a monitor is the sense of scale - I love looking out over the wing of a Hornet and *feeling* how big the plane is, very cool. But yeah, after ten minutes, I find myself wanting my monitor. I will say this though, VR is incredible, but I feel it really lends itself to different formats, like some of the experiences designed specifically for VR. I'm sure the tech will get more and more impressive for flight sims, as the FOV and resolution increases, and ergonomics become better integrated.

F-117. It would offer a combat experience we are yet to see in DCS, it has historical significance, and shares a number of existing systems. It would also work well with the current maps, and be a pretty thrilling experience, trusting your technology to keep you safe.

Ah, that makes sense. Is there any way around this to get the chrome bare metal look? Or will it require the dev to update the shaders?

Perhaps Skate or someone can help with a problem I'm having getting a reflective bare metal look on the F-5. Currently I can get it looking reasonably good in the object viewer when I load up "f-5e3_lod_00.edm" with the spec files, as you can see in the first image. But when I load in-game, or load "f-5e3.lods" It returns to a neutral, glossy painted look in direct sunlight. I have tried converting to roughmets, which again, works with the .edm files, but not with the .lods file, or when I view the model in game. Dramatically changing the spec channel values (or roughmet channel values) only makes a minor difference - either it looks glossy painted, or matte painted, when viewing in-game. Only the "f-5e3_lod_00.edm" responds well to changes in the spec or roughmet. f-5e3_lod_00.edm f-5e3.lods (in game)

Yes I am familiar with Skate's guide. It would appear that renaming the map to "RoughMet", and changing the channel from "2" to "13" does detect the RoughMet, however regardless of changes to the map, it looks the same. Is the F-5 governed by a json file that is overruling my spec map changes?

I am trying to replicate the chrome texture, found on the rear of the fuselage (nozzles), across the entire fuselage. I can achieve this in the model viewer, but in-game, the fuselage looks glossy but painted, not chrome/metallic. I have looked extensively at the spec maps, and I can't see anything different on the R, G, B channels for the nozzles compared to the rest of the airframe. Does anyone have any suggestions about how to achieve a chrome look for the rest of the airframe?

Solved. Here's what seemed to work - I could load the device profile ("Step 1: Load Device Profile") For the throttle, which allowed me to update the firmware, however I still couldn't load the stick, it kept saying "version not supported". When I tried to "Import Profile from file" (bottom left), it came up with a PCB error, so I shut down the Config tool and did this: 1 - Open config tool 2 - Select "Import profile from file" (bottom left) 3 - Select the profile that matches configuration (for me "VPC MT50 + MT50 [PCBv06].cnfv06") 4 - "Step 1: Load Device Profile" - I didn't get a PCB error this time - and it says the correct device in the top right of the window. 5 - Firmware update Then follow the usual process to calibrate. I had a "not synced" message in the top left until I completed the calibration process (not sure why).

The profile won’t load. The button doesn’t do anything, see the original post in this thread. So I can’t update firmware for the joystick.

Can anyone post the solution to this issue? I'm having the same problem. I have opened a ticket. Throttle detects fine, but the stick doesn't (VPC_Configurator_Light_20180828 )

I also own both the VirPil and VKB stick offerings. Couple of points to add on the gimbals. The VirPil has a shorter throw but a longer extension, which subjectively feels better for centre floor mounting, as you don’t have move your wrist as much for comparable fidelity. The compression spring design also feels better in my opinion, as does the tension tuning screws. Also a compression spring is less likely to break over time. Just thought it was worth mentioning.

Brilliant, thanks Baur

What size screw is needed to thread the four attachment points under the base plate? I am fastening the throttle to a plywood mount, and would prefer to use these attachment points, not the corner holes.

Pleased you guys are enjoying these skins!

Introducing F/A-18 Hornet RAAF Pack 2.0 - 3SQN A21-17 https://www.digitalcombatsimulator.com/en/files/3301625/ A21-17 appears as it did in June 2017. This low visibility scheme is indicative of any 2010’s 3 Sqn Hornet, and represents the final year of the Hornet in 3 Sqn service, before the remaining aircraft were transferred to 77 Sqn to make way for the F-35A. The tail displays the 3 Sqn eagle carrying a bomb logo, with the Southern Cross backdrop, modernised from the mid 2000’s to have a more defined appearance. The fuselage arrows are inverted in colour, with the 3 Sqn eagle crest as the centre-point. Many of the panels have been repainted and show varying amounts of paint fade. There are minimal fluid deposits on the wings and tail. The most notable element is the anti-slip surface on the leading edge extensions, which is inverted from its usual black or faded gray appearance.