Search results

I would if I could. Orbiter inserts that after running.

I wouldn't think so. You can specify paths without any quotes at all. They're just there so paths with spaces can be used. After testing, it didn't make any difference.

Okay. I've been trying some different things and finally made some progress. For some reason Orbiter is not reading my TextureDir config. So it never reads any Textures. I only managed to get stuff working after I copied over my Textures folder from Orbiter 2016 to the Beta. Too bad Orbiter...

I got exactly that output. DX9 works perfectly fine, considering the D3D9Client works on the main version of Orbiter2016. It must be something related to either the beta itself or the beta plugin.

Positive. I've attached an image of the modules and plugin directory and included a video to show exactly what's happening.

Yes, I do. Reference my original post.

That's what I meant. Orbiter2016 with r995 does work. OrbiterBeta with r996M does not work.

I don't have anything in System besides a Speech folder. I do have those dlls in System32 though. I went ahead and tested r995 on Orbiter2016 (non-beta) and that did work. It's just the Beta that doesn't work. Suggesting that the dx runtime is not the issue.

I did indeed run the setup after extraction.

Yes. I installed this and this. Are those the right ones?

Orbiter crash on plugin load Hey all, I recently got a new PC and I'm in the process of setting up Orbiter and my dev environment for NASSP again. I'm running into issues getting the DXD9Client (r996M) to work with rev. 84 of Orbiter Beta. After I've extracted the client into my beta...

I told you this in the other thread. If you want us to help we need to know what the problem is. Describe your issue, what have you tried? How can we reproduce the issue? If Orbiter crashes, provide the logs. We cannot guess what your problem might be if you don't give us any information about...

We need more details than that.

I do sometimes notice restarts when coming in and out of time acceleration. I have not been able to consistently reproduce this issue but my best guess it has something to do with the parity ropes that were added some time ago.

We've seen some AGCs get corrupted with time acceleration in the past. Wonder if this has anything to do with it.

A lot of development discussion takes place on IRC. Server: irc.libera.chat Port: 6665-6667 (SSL: 6697, 7000, 7070) Channel: #nassp Webchat if you don't wish to install a client: https://web.libera.chat/ Connecting: https://libera.chat/guides/connect Registering your nickname...

Happy to be here. Now I can finally use the forum without having to try to load it 7 times.

Hey everyone! :hello: My name is Thymo, I'm a developer on the Project Apollo - NASSP and VirtualAGC projects. Since we're moving to here I thought I'd introduce myself. I'm currently an IT student at Saxion University of Applied Sciences in The Netherlands. A couple of my interests are Linux...

FYI We no longer support Simple AGC (along with the rest of quickstart mode) so that page may not always apply to VirtualAGC.