Holly Molly, an update that I never expected! Nice one guys!
Cheers guys. I'll keep the clouds as I think transitioning in and out of them looks pretty cool and fairly realistic.
I realized that AFS2 only draws clouds in about a 5 mile area around me. I cant find any settings to extend that so that clouds further away are drawn.
Is this how it is, or can we change it?
Hm, this thread is becoming yet another whish-list - don't get me wrong, it's alright but knowing how development works in general these will most likely never materialize.
Both the Event Viewer and Task Scheduler are native part of Windows 7. You can access them by clicking on Start menu and right click on Computer. Select Manage from the pop-up menu:
You'll see both Event Finder and Task manager on the top-right.
From here you can disable those tasks as per the screenshot in my previous post.
Sure thing mate, what specifically would you like to know?
Happy to report that I found the culprit, and to be honest I would've never in a 1000 years thought this could be it. So, whenever AFS2 froze I checked the Event Logs. There was this one curious item that keep popping up at the time of the simulator crash: the Application Experience Service started. So, I Googled up on this and found that there are two scheduled events that control this silly think. I disabled them both in Task Scheduler and Viola! no more freezes. Here is the screenshot of the two Tasks (AitAgent and ProgramData Updater) disabled:
This might be some useful info for the Devs as this never happened before the last update - not sure what the connection is though.
The main challenge with this freeze issue is that AFS2 doesn't seem to generate an error log about it (or it's just hidden in another location).
I've been using AFS2 for quite some time but since the last update I experience a strange issue. The simulator "freezes" mid-flight, and I have to shut down the AFS2 process altogether - otherwise it just hangs.
I tried verifying the files through Steam, but it didn't find any issues. Then out of curiosity I also installed AFS2 on another PC - it produced the same issue. I had a look at the log file but there was nothing useful there. I attached a screenshot showing the frozen sim and the resource usage at that time. I also attached the logfile. Any ideas where should I look for further troubleshooting? Anyone else with this issue?
My PC specs are: HP Elite 180a, 12GB RAM, GTX750, Samsung 1TB SSD
Thanks in advance
Just wanted to confirm that I just downloaded the SDK and converted the DR400 with no issues for the current version.
Rodeo - Much appreciated, thanks a lot! I've been working on sceneries for some time but I'm totally new to AC3D - I thought it would be something basic like that.
Edward - sure, I'm aware that there will be a tutorial at some point and I didn't want to seem inpatient, I know how busy these guys are, but I was keen on starting my little project. Once I'm done I'll be uploading a tutorial myself.
4 of the most important things I couldn't work out in AC3D yet is:
1) how to set the scale once I inserted my reference image.
2) how was that mesh of vertices generated for the airport area
3) how was the runway sliced up (manually)?
4) how was the airport mesh merged with the runway mesh?
I've been tryig to find answers for 2 days now - no tutorial on these (I guess basic) steps anywhere for AC3D. It must be the least documented awesome program ever...
Anyone with a bit of experience? (Rodeo? :))
Thanks for all your help guys,
It was my silly mistake as pointed out by Rodeo, I've put in the co-ordinates in a reverse order.
I'm rendering a small area and the process finishes successfully, but for some reason the images are not generated. I'm a bit suspicious about how GeoConvert converted the TFW files to AIC, more particurarly the "steps_per_pixel" values:
Original TFW file:
AIC file generated:
...and for reference, here's my simple TMC file:
<[uint32] [level] >
<[vector2_float64] [lonlat_min] [-45.56 169.76]>
<[vector2_float64] [lonlat_max] [-45.91 170.74]>
<[uint32] [level] >
<[vector2_float64] [lonlat_min] [-45.56 169.76]>
<[vector2_float64] [lonlat_max] [-45.91 170.74]>
...and here is the log for the conversion:
0.00-tmmodule: init modules=(tmsystimer=ok) done
0.00-tmmodule: Program version 1.2.3
0.00-tmmodule: Copyright (C) 1998-2017 IPACS
0.00-tmsyswin: memory=(physical=12247MB, avail=7227MB) (virtual=15317MB, avail=8388607MB) (40 in use)
0.00-tmsyswin: operating system (7.1)= Microsoft Windows 7 SP1
0.01-tmsyswin: monitor size = 474 296
0.01-tmmodule: fullscreen modes=(1024x768x32x60) (1152x864x32x60) (1280x768x32x60) (1280x800x32x60) (1280x960x32x60) (1280x1024x32x60) (1360x768x32x60) (1366x768x32x60) (1600x900x32x60) (1600x1024x32x60) (1680x1050x32x60) (1440x900x16x60) (1600x1000x16x60)
0.07-tmsysprogram: application init. commandline='dunedin.tmc' userfolder='./'
0.07-tmsyswin: init window=(mdf=60Hz) (window=0x0x656x518) (client=640x480) (screen=1680x1050) (32bpp) (60Hz) (windowed mode)
0.10-tmmodule: initializing directx= done
1.55-dummy: resolution=640px ss=474.00mm -> res=640
1.55-dummy: create fbo = 640 480
1.57-tmrenderer_font: loading font 'texture/fontdisplay.tff'=(512x512) (h=37) (nc=8365) ok
1.58-elevation: loading configuration file 'dunedin.tmc'= 2 regions
1.60-elevation: 26 input aerial images found:
1.60-elevation: file './input_aerial_images/92M3S-92L78.tif' -> mask='' topleft=(170.743293 -45.602770) sppx=(0.000027 -0.000034) image=1314x7200 flipv=1
1.60-elevation: file './input_aerial_images/92M3Q-92L77.tif' -> mask='' topleft=(170.414625 -45.356269) sppx=(0.000027 -0.000034) image=6031x7200 flipv=1
1.60-elevation: file './input_aerial_images/92M3Q-92L76.tif' -> mask='' topleft=(170.414628 -45.261046) sppx=(0.000034 -0.000034) image=1312x2781 flipv=1
1.60-elevation: file './input_aerial_images/92M3S-92L79.tif' -> mask='' topleft=(170.743297 -45.849271) sppx=(0.000034 -0.000034) image=909x1023 flipv=1
1.60-elevation: file './input_aerial_images/92M3S-92L77.tif' -> mask='' topleft=(170.743297 -45.527257) sppx=(0.000034 -0.000034) image=383x2206 flipv=1
1.60-elevation: file './input_aerial_images/92M3P-92L79.tif' -> mask='' topleft=(170.250294 -45.849271) sppx=(0.000034 -0.000034) image=4800x5436 flipv=1
1.60-elevation: file './input_aerial_images/92M3P-92L77.tif' -> mask='' topleft=(170.250294 -45.356269) sppx=(0.000034 -0.000034) image=4800x7200 flipv=1
1.60-elevation: file './input_aerial_images/92M3P-92L78.tif' -> mask='' topleft=(170.250294 -45.602770) sppx=(0.000034 -0.000034) image=4800x7200 flipv=1
1.61-elevation: file './input_aerial_images/92M3R-92L78.tif' -> mask='' topleft=(170.578963 -45.602770) sppx=(0.000034 -0.000034) image=4800x7200 flipv=1
1.61-elevation: file './input_aerial_images/92M3R-92L79.tif' -> mask='' topleft=(170.578963 -45.849271) sppx=(0.000034 -0.000034) image=4800x1951 flipv=1
1.61-elevation: file './input_aerial_images/92M3R-92L77.tif' -> mask='' topleft=(170.578963 -45.491486) sppx=(0.000034 -0.000034) image=4800x3250 flipv=1
1.61-elevation: file './input_aerial_images/92M3Q-92L78.tif' -> mask='' topleft=(170.414628 -45.602770) sppx=(0.000034 -0.000034) image=4800x7200 flipv=1
1.61-elevation: file './input_aerial_images/92M3Q-92L79.tif' -> mask='' topleft=(170.414628 -45.849271) sppx=(0.000034 -0.000034) image=4800x2784 flipv=1
1.61-elevation: file './input_aerial_images/92M3M-92L78.tif' -> mask='' topleft=(169.921626 -45.602770) sppx=(0.000034 -0.000034) image=4800x7200 flipv=1
1.61-elevation: file './input_aerial_images/92M3M-92L79.tif' -> mask='' topleft=(169.921626 -45.849271) sppx=(0.000034 -0.000034) image=4800x3410 flipv=1
1.61-elevation: file './input_aerial_images/92M3L-92L78.tif' -> mask='' topleft=(169.757291 -45.602770) sppx=(0.000034 -0.000034) image=4800x7200 flipv=1
1.62-elevation: file './input_aerial_images/92M3M-92L77.tif' -> mask='' topleft=(169.921626 -45.356269) sppx=(0.000034 -0.000034) image=4800x7200 flipv=1
1.62-elevation: file './input_aerial_images/92M3N-92L76.tif' -> mask='' topleft=(170.085960 -45.223272) sppx=(0.000034 -0.000034) image=4800x3885 flipv=1
1.62-elevation: file './input_aerial_images/92M3N-92L79.tif' -> mask='' topleft=(170.085960 -45.849271) sppx=(0.000034 -0.000034) image=4800x6360 flipv=1
1.62-elevation: file './input_aerial_images/92M3P-92L76.tif' -> mask='' topleft=(170.250294 -45.224800) sppx=(0.000034 -0.000034) image=4800x3840 flipv=1
1.62-elevation: file './input_aerial_images/92M3N-92L77.tif' -> mask='' topleft=(170.085960 -45.356269) sppx=(0.000034 -0.000034) image=4800x7200 flipv=1
1.62-elevation: file './input_aerial_images/92M3N-92L78.tif' -> mask='' topleft=(170.085960 -45.602770) sppx=(0.000034 -0.000034) image=4800x7200 flipv=1
1.63-elevation: file './input_aerial_images/92M3L-92L77.tif' -> mask='' topleft=(169.768574 -45.441837) sppx=(0.000034 -0.000034) image=4470x4701 flipv=1
1.63-elevation: file './input_aerial_images/92M3L-92L79.tif' -> mask='' topleft=(169.877179 -45.849271) sppx=(0.000034 -0.000034) image=1298x445 flipv=1
1.63-elevation: file './input_aerial_images/92M3K-92L78.tif' -> mask='' topleft=(169.728525 -45.664869) sppx=(0.000034 -0.000034) image=840x2859 flipv=1
1.63-elevation: file './input_aerial_images/92M3M-92L76.tif' -> mask='' topleft=(170.058426 -45.349647) sppx=(0.000034 -0.000034) image=804x193 flipv=1
1.63-elevation: building tile list for level 9
1.63-elevation: grid -> 24410.34 24474.06 13395.81 13904.19 -> 128.00
1.63-elevation: done -> 190 191 104 108 tiles=10
39.00-elevation: building tile list for level 11
39.00-elevation: grid -> 24410.34 24474.06 13395.81 13904.19 -> 32.00
39.00-elevation: done -> 762 764 418 434 tiles=51
257.40-tmmodule: render thread exited
Any thoughts? Thanks a lot!
Well said HiFlyer, well said!
On a related note, I'm confident that 60%-70% of the flight simulator fans are interested in other types of simulation too (trucks, trains,etc). So instead of "nagging" IPACS every 2 weeks for updates we could just enjoy the other half-a-million enjoyable products out there while we're "waiting". For example I find TrainSim World an awesome little product (especially since they optimized it), there are a bunch of new space sims, and some VR stuff - there's plenty to do out there, that leaves us with no real reason for complaining about progress. I don't mean to be arrogant - believe me I'm just as excited about the updates as you guys are, but let's get real, and give the developers a break. With the never-ending requests for more and more and more we just give them more pressure, and frustration which slows everything down. What they need now is a positive kind of support - happy to see that there is plenty of that on this forum too.
Jan, yes, it's a quick and dirty way, kind of ignoring the .tdm files, but I haven't had a chance to work out how fine tuning works and what the numbers refer to. I'd be keen to get involved in sound development, I have the gear and the experience to create sound environments, but I guess there is not much point until the sound engine is finalized.
Good point about trying stereo/44100KHZ - I'll see what happens.
I'd be happy to share but I used a previously purchased 3rd party sound from TSS, so I can't share the files, but will update a video shortly.
Yes the current aircraft sounds might be limited to mono and 22500KHz, but the actual sound engine is surprisingly good. I was able to add much more realistic sounds to the jets, and it was a fairly quick process.
I'm sure most of you have quite a few addons for P3D or FSX with pretty good sounds. Luckily those addons use WAV sound files - that's the raw format required by the AFS2 converter tool. So, here is a brief tutorial of how you can create your own sounds for any aircraft in AFS2:
Obviously you'll need the SDK and the aircraft conversion tool installed to do this - please do that first if you haven't done so already.
1) Identify the number of engine sounds for the specific aircraft you'd like to create sounds for. Let's have a look in your C172 folder (under /Aerolfy FS 2 Flight Simulator/Aircraft). We're looking for files with .tsb extension. With the Cessna you'll find quite a few .tsb files but their name is a perfect hint. For example ext1000rpm.tsb means the external sound file for 1000RPM. There is 6 internal and 6 external engine sounds for the cessna for 6 different RPM ranges. However, the cessna sounds are pretty spot on, so let's "update" another aircraft. We all love the A320, don't we? Unfortunately the sounds it comes with don't really do it justice. So, again, have a look in its folder and search for .tsb files. As before, based on the file names there are basically 2 X 3 files (3 for external and 3 for internal), with names like idle, half, and full. There is also a reverse thrust one, but let's focus on the internal ones for now, those three .wav files for idle power, half power and full power.
2) Getting raw sound files is pretty simple: go to AVSIM, or Flightsim.com and download a freeware soundpack, or use any 3rd party soundsets you purchased before, then choose the appropriate .wav files from them that will represent those 3 power settings.
3) Now we'll have to make sure those .wav files are prepared for conversion. First let's rename them as per the original files. For example the sound file you chose for the idle engine sound should be called "a320-idle-intern.wav". In other words, give them the same name as the tsb file only with wav extension.
For the rest of the sound preparation tasks I'll use Audacity, but you're free to use your favorite sound editor. For each sound file do the following: "
- Open the file in Audacity
- Click on "Stereo Track to Mono" on the Tracks menu at the top of the window
- Click on "Resample..." on the Tracks menu and choose 22500
- Click "Export..." in the File menu, provide a file name, and choose "WAV (Microsoft) Signed 16bit PCM" as the format
Once you completed these steps for all files, they will be ready to be converted
4) We'll create a folder under the /aricraft_workshop directory of the SDK root folder. Make sure you only use lower case and numbers for the name of this folder. I'm going to use "sound001" for simplicity. Now, copy the prepared wav files into this folder, and also copy the following 3 files from the /dr400 folder (that's also in the aircraft_workshop folder): model.tmc, dr400.tgi, dr400.tmd. This is all you need for the sound conversion.
5) Now, right-click the sound001 folder (with the raw files in it) and choose the "Aerofly FS 2 Aircraft Converter" from the pop-up menu. You can click on the green Convert button - however you won't need to wait till the whole conversion process finishes though. The converter will start with the WAV files luckily, so when you see it working on things like "geometry" that means the sound files are already converted, so you can click on EXIT.
6) You'll find your converted files here: C:\Users\<username>\Documents\Aerofly FS 2\aircraft\sound001
7) Create a backup of the sound files you're about to replace (under <AFS2 root>\aircraft\a320\). In this scenario we'll replace the 3 internal engine sound files: a320-idle-intern.tsb, a320-half-intern.tsb and a320-full-intern.tsb. BACK THEM UP! No really, back them up!
Now you can copy and overwrite the original .tsb files with the ones created by the conversion tool (from C:\Users\<username>\Documents\Aerofly FS 2\aircraft\sound001 into <AFS2 root>\aircraft\a320\). I'd recommend that you delete the sound001 directory (the one under your Document folder) after you copied the files from it so there won't be any mix-ups with other sound files you might convert later - this way you always start the conversion with a "clean slate".
9) Test your sounds. Load up the plane and try all power settings. I found that the AFS2 sound engine does a great job with aligning them and combing them together seamlessly.
That's pretty much it. If you want to make some adjustment (volume, EQ) do that on your raw files and convert them again. Once you get used to the process it won't take more than 5-6 minutes including testing.
You can customize all aircraft sounds using this process, not just the engine sounds. However, it's important that engine sounds have to be infinite loops, while others (like the autopilot disengage sound for instance) don't need to be looped.
In case you have any questions or my explanation wasn't clear on a certain step, let me know.
PS: If you screwed up the back-up step, you can always use the Steam File Integrity check to restore the factory files.
The scenery and the colours in Aerofly FS2 are awesome - so when I realized that the A320 has a "hazey" glass texture that makes everything look "washed out" and pale I decided to fix it. It's 3 simple steps:
1) Rename the a320_glass_color.ttx file in your /aircraft/a320 directory
2) Copy the cockpit_glass_color.ttx file from the /b737 to the /a320
3) Rename cockpit_glass_color.ttx to a320_glass_color.ttx,
...and you're done.
Enjoy the clear colorful views.