Jump to content

Pete Dowson

Commercial Member
  • Content Count

    2,439
  • Donations

    $50.00 
  • Joined

  • Last visited

Everything posted by Pete Dowson

  1. Ah, Is that a programmable action? e.g via a Windows Message? Ouch. Possibly not. It would probably need more indirect methods like Windows messages or DDE/Pipe methods. Pete
  2. WCF? I had to look that up. Ouch. Seems that I'll have to write a separate program for the Traffic Limiter, then, unless John agrees to the work needed in FSUIPC. I see RemoveAIGFPSimObject -> Disable the reinjection of the aircraft bind to this objectID. Is the ObjectID the same one I would get from P3D, the one currently used to delete the object and by other traffic programs to try to control them? Also: We will provide a C#-Library containing the Interface/Contract as well as the Client-Class, for direct integration in your project. I don't know C# and even avoid the Class elements of C++, being an old ASM and C programmer, too long in the tooth to start new things. So, is a C# library linkable and usable in a C program? If not, will there be a DLL version to link to? Regards Pete P.S. I followed your link to the Microsoft WCF documentation. The downloaded PDF is 412 pages!!! 😞
  3. Kaii3, does this update to AITC inject and re-inject traffic in big batches still, defeating frame rate control by those traffic limiters which attempt to delete some (eg like FSUIPC's)? You have said you would work something out. Pete
  4. The "bubble radius" is the area around the user which can contain AI Traffic. I think it is generally understood to be 80 km radius from your location. BGL traffic flying into the bubble is generated at that distance -- injected traffic can be introduced anywhere within the bubble. The only other way BGL traffic can be introduced is in 'sleeping' state at gates or parking places. Pete
  5. That makes no sense. It doesn't do anything when you don't run it. If you run it to set overclocking it does that via the BIOS settings, and you can undo them all either in AI Suite or in the BIOS. And it doesn't have anything to do with video -- that's MSI Afterburner. BTW I saved several different sets of settings in AI Suite ("profiles"), with one which was actually underclocked from the default for the mobo -- just in case I ran into an problems and needed to test things in a presumably less stressed setup. Pete
  6. That's really all AI Suite does if you use its automatic mode to find the best stable settings. I let it do that then went one of its steps back to ensure some headroom. But yes, you can mess things up real good if you mess with its sliders yourself, as of course you can directly in the BIOS. Annoyingly (for me) AI Suite does not touch the memory clocking or voltage, nor the GPU -- it only deals with CPU clocks and voltages. I had to venture into the BIOS to turn my memory clock down from its nominal 4500 MHz rating to 3900 MHz in order to achieve my stable setting of 5.5 GHz on all cores. My RTX Titan GPU was overclocked at source so I've not touched that. BTW, I've never had any DXGI failures -- one of the lucky ones i assume! 😉 Pete
  7. It's a DLL loading into P3D, just like FSUIPC, so it should be terminating automatically when P3D closes. If it doesn't, if it's hanging instead, then the P3D process must also still be running, needing terminating forcibly via Task Manager. If it is doing this regularly it needs to be reported to Navigraph for fixing. Pete
  8. rob0203 does though. I was exchanging notes with him before your good self. 😉 Pete
  9. If running VoxATC on a networked PC, is that where the keystrokes go and these 'windows' appear? Otherwise that's not much use to me. And is there some place where the "recent conversations" and current ones appear in file form so I can read it and display on a screen in my cockpit? I've read the whole of the VoxATC User manual and there is nothing there about the things I need to know. Pete
  10. Yes. I think that is why I abandoned my attempts when I tried it on its free trial period. I think also another problem I had with it was its sound input/output was on the Sim PC, not the networked one. Is that still the case? My headsets and, indeed, all my SAPI Voices, are on my Networked PC and I'm not about to try altering that. The Sim PC is busy with aircraft related sounds through multiple speakers. On my P2A PC I can switch the ATC voice between the headsets and the overhead using a switch on the overhead which tells P2A to change the sound device in use. I might have another look at VoxATC but it is sounding still rather unsuitable. I'm quite pleased with P2A and it will have 'adequate' AI interaction one day. just not full control as it isn't injecting them itself. I'm surprised VoxATC finds enough time to do all that and still provide good user interaction. Pete
  11. Oh, so the code is in a gauge just so it gets installed within P3D? I wonder what the author didn't have it loading as a DLL, which would seem more sensible and convenient than altering all the Panel CFGs. I would need a shortcut keypress for that -- no way can i manipulate P3D menus on my curved screen, and especially not from within the cockpit. If it is loaded with the aircraft I wonder why it cannot be "started" by the part running on the networked PC? Strange. Pete
  12. So are those gauges invisible? I don't understand what they are for. Pete
  13. Is that a Window in a P3D addons option, or on the main Windows screen? Can't it be set to be enabled automatically? How much of that do you need to refer to whilst flying? Is there a way of sending conversation details to another PC? Pete
  14. Further on my last: A quick look on the VOXATC Forum seems to indicate that there is still a "panel setup" to run, installing one or two gauges. With ProSim implementing all of my 738 systems externally, there is no 'panel'. What would VOXATC do about that? Pete
  15. With no interference (eg via gauges) on the P3D screen? Does it produce a conversation log which I could then display on another PC screen inside the cockpit? I did some research on this with VOXATC and couldn't find a solution I was really happy with. Maybe some things have changed since then. Pete
  16. I got that a lot with RC too, and ProATC/X for that matter. The problem is that they freeze taxiing traffic to stop it encroaching on the runway when you are landing or cleared for takeoff, but aren't easily able to deal with traffic seemingly landing on a "different" runway. I think that's why the use of one or more of the other little utilities for controlling AI is a good idea. Another way to avoid "wrong end" landings and takeoffs is to ensure the ground wind speed is always above a certain minimum (something like 7 knots I think), enforcing the AI to use the "correct" runways. Not foolproof but it helps. I think AS has such an option. I do understand that VOXATC is better in dealing with AI traffic, and not only conversing with them. After all, having injected the traffic it does have full control over them. It is just a shame its implementation does not suit my enclosed cockpit with the outside world on a big curved screen. Pete Pete
  17. As does Pilot2ATC and, I seem to remember, so does ProATC/X. But not RC or PF3. I run P2A on a separate PC, and have its conversation log scrolling on a small screen inside my cockpit. I couldn't find any way to do either successfully with VoxATC. Agreed that P2A's lack of vocal interaction with AI traffic is a detraction. It is on the developer's list. P2A does have the benefit of continued development and a very responsive author. Pete
  18. 😉 Yes. Note the "Vox" in the name! Pete
  19. I think it injects traffic, same as UTLive and AIGTC. The only part of the AIG installation it will be using are the aircraft models and liveries. It makes use of whatever aircraft are available. I don't know how realistic its choice of aircraft for airports or times and routes is. Like Pilot2ATC it is voice controlled, but unlike Pilot2ATC it seems to need stuff installed and displayed on the P3D PC, which is why I've avoided it in favour of P2A. Pete
  20. Anywhere you like on the same PC. Best to create a folder called MakeRwys and put it in there. Point P2A to that folder for the data. Pete
  21. Thanks. I think the problem is that your Windows 10 (I assume?) appears not to have long pathnames allowed. The normal maximum is 260 characters, but this restriction can be overridden by using that \\?\ prefix. From Windows documents I'd assumed that this would work no matter which build of Windows is being used -- it was okay on three different versions on PC's I have. However, it is noticeable that the last line logged on your system is showing a pathname longer than 260 (discounting the "" envelope, which isn't used in the actual windows calls). In fact it's the first path longer than 260, at just 261 characters! Perhaps I should log also the version and build number of the Windows version in use. But could you tell me (use WinVer) please? And maybe try to update. Using Google I have found this: 4.3 Enabling Windows Long Path (Windows 10 - 1803 build) Click Window key and type gpedit. msc, then press the Enter key. ... Navigate to Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem. Double click Enable NTFS long paths. Select Enabled, then click OK. Could you try that please? There's also a way of editing the Registry instead. See https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/ Let me know please. Pete
  22. Thanks. They are identical to mine. Without being able to reproduce the problem here, I am stuck really. What is most puzzling is the missing "scenerylist.txt" file. That is produced before the folders are processed. Please ZIP up the entire Scenery.txt file and send it. Something odd must have happened before the file processing stage started. Also, please tell me where you installed MakeRwys.exe -- in a folder of its own? I'm having some difficulty trying to understand exactly what "Exception code: 0xc0000409" actually means. It isn't in the official MS lists. This website: https://www.minitool.com/news/0xc0000409.html suggests it might be a system error rather than a specific program bug, and that you should run system file checker. I also found this How to fix the 0xc0000409 error Press Windows key + R to open up a Run window. ... In the Troubleshooting tab, click on Windows Update (under the Get up and running tab) and choose Run the troubleshooter. Wait until the initial wizard detects the problem that is causing the issue. Pete
  23. No! Certainly not! Thanks. I'll look at that, but it might be a while. I suspect all it will show is data being read which makes no sense. It might be quicker for you to trying repairing/reinstalling. If I do manage to locate the problem in MakeRwys processing it is likely that all I can do with it is to terminate tidily with an error message, which still wouldn't give you the results you need. If I can by-pass the error then I will. I'm wondering if it would help if you sent me the contents of those two folders. You could try ZIPping them up and sending to petedowson@btconnect.com. Pete
  24. If things were okay the next line would be: "\\?\C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\fs-devmode\Edition\templates\AssetGroups\SimObjects\airplanes\singleprop-empty\SimObjects\Airplanes\MyCompany_AssetName\texture\" ***** Processing MSFS official scenery (Asobo=1) so I'd guess that there's some corruption either in that soundai folder, or in this texture folder. Was there any crash data for MakeRunways in the Windows Even Viewer? Please check. There should be a SceneryList.txt file as well -- please check. That is produced before this processing begins. If that completes then there is definitely some error in one of those two folders I mentioned. It would need to be repaired somehow. I'm not sure whether MSFS offers any repair options for installation -- if not then I think it will mean a re-install. Going by the pathname, the files where it stops seem to be related to devmode. Perhaps disabling devmode with remove them from the list. Pete
  25. "Runways.txt" is the log showing what happened, so you need to look at that. Pete
×
×
  • Create New...