Since I have noticed if I'm not coding enough on PCem the vNext builds will expire and will not allow you to download. I now adjusted the Actions to also upload to my CDN and will be assesable at https://pcem-dev-builds.cdn.ntgecdn.com/ To get a build using the CDN do the following. Get the artifact...

I am going to close this, Its for an older release and don't need to keep getting responses on it when said person is no longer maintaining anymore.

Might look into adding things like this in a future release, but it be a while.

emily wrote: ↑Wed 09 Aug, 2023 10:20 pm

MichaelJManley wrote: ↑Wed 09 Aug, 2023 1:20 am I didn't even half to answer this but it felt good to answer such a retarded ass notion! lol.

That is a very, very rude remark, Michael

Well, honestly, I can say it's kind of rude to call me fake lol. What you expect me to do?

I see why Sarah gave up, Well, I don't know if you have been here when v17 was just released, but there was a contributor called Battler who was also a developer of an emulator called 86Box, and he was trying to ram 86Box down her throat. She got furious, to the point that she actually used the &qu...

I think Michael is doing a good job. Until he has something to announce or release to the public, it makes no sense to just add whimsical or half-finished features to PCem. No one likes a half-finished program in need of constant fixes, patches and updates. When was the last time PCem crashed? In m...

emily wrote: ↑Wed 09 Aug, 2023 10:26 pm You do a good job of continuing Sarah's legacy of irritability: I was saying the same as what you just said:
you simply keep an eye on things, PCem doesn't have to be your priority, you're just the maintainer.

Well comment was missing some context, so I thought it was coming out as sarcasm

PCem is not a priority for him. He's just the maintainer after all. You do know what a maintainer is right? In free and open source software and inner source software, a software maintainer or package maintainer is usually one or more people who build source code into a binary package for distribut...

I have a feeling that "Michael J. Manley" doesn't actually exist. At some point in the development of CCS 64, a Commodore 64 emulator, the author Peter Hakan Sundell couldn't withstand the pressure from users and after vanishing for a while, he apparently handed over everything to a Stuar...

you can get basically the latest and greatest from GitHub, https://github.com/sarah-walker-pcem/pcem/actions/workflows/test-release-builds.yml All of those links have "expired". Does anyone have a link to the last build from 3 months ago? Yeah… I see that builds over time get removed. I a...

leilei wrote: ↑Wed 15 Feb, 2023 7:04 am It's now in C:\Users\username\.pcem\roms (for platform consistency)

And the most recent build, if you create a .pcem folder before running, it will become the directory for configuration.
Added that feature for the people who ran it portably

The ironic thing is you can get basically the latest and greatest from GitHub, https://github.com/sarah-walker-pcem/pc ... builds.yml

So there, thats your v18 if you can't wait for stable. People have a life, can't always develop on PCem.

When will this new version of PCem V18 be released? As it was already mentioned: February 30th. It will bring Pentium 4 and GeForce 6 emulation. LOL, yes why stop there how about Core 2 Duo support! But for reals, I am the only developer, and also have other projects I am working on. It's on my lis...

Yes, this is something that comes up over and over and over.

PCem will NEVER be a virtualiser. The whole point of PCem is to emulate the hardware and basically give you a 1 to 1 copy of older hardware, even to the bios/chipset level.

Emulation != Virtualization.

am I'm missing something? The new path is: %HOMEPATH%\.pcem I do plan on resolving this in if it detects a .pcem folder with the EXE, it will use that instead of the home folder. Basically gives it portable mode. If you dont add that folder, it will default to %HOMEPATH%\.pcem I know that change wa...

Sooga wrote: ↑Mon 05 Sep, 2022 1:53 am How's PCEM V18 going now that we are onto September? Maybe it will be released on the 21st night of September?

Working on it, Changing an entire GUI framework does take time, it's a major overhaul. And PCem isn't my day job so I don't get 24/7 to code on it.

@unreal: LOL be careful not to actually quote the link, had to modify your post @marzban2030: Post a romset again and you will be banned, we don't allow linking of ROMs due to copyright reasons. PCem just veers on the side of caution so that we don't get shut down. There is a few exceptions (Like Ge...

So is PCEM dead? No news for a long time. I hope the new manager didn't get immediately overwhelmed due to so much focus on 'realism'. If you feel overwhelmed don't be afraid to make sacrifices for performance,etc whatever you feel is necessary to keep the project alive. It's all about balance baby...

...V18 will be switching to Qt ... Qt 4.x was good but 5 or 6 is "very nice" for redistibute... 1.5MB of pcem + 200 MB Qt shit... Really only affects Windows, Linux users don't have that issue, which is kinda what I develop for, though I try to keep Windows still functional as it's a big ...

V18 will be switching to Qt This may regress XP/Vista/7/8/8.1 support. Several emulators moving to QT (PCSX2, Dolphin) gave up 7 because they had no choice in the matter when that decision's from upstream and/or develop on Win10/linux unaware of the platform regression creep issues. OTOH it's great...

See top for new information

Printer support is experimental. The reason it fails to compile is due to API changes and it's not been put into the printer code yet.

The README does state that experimental code may not work or build.

Arjen42 wrote: ↑Sat 18 Jun, 2022 7:10 pm How can we download dev builds?

In GitHub Actions, https://github.com/sarah-walker-pcem/pcem/actions

Jonathan McEvoy wrote: ↑Sat 18 Jun, 2022 11:06 pm Will there be a new stable version called PCem V18 later in 2022?

Working on a release this year, finishing the plugin API and some bug fixes so hopefully soon!

EDIT: I am going to retract this statement due to the recent announcement on GitHub, Since I am doing some major changes to the core environment, dev builds are going to be very different from V17, so I will accept bug reports, and ill just check to see if they are still an issue on V18 V18 will be ...

The capability is not fully implemented, that's why GitHub builds its disabled by default. The API is still being planned.

The location will be ~/.pcem/plugins and it needs to have a .pplg extension.

Did you ever get a backtrace for that crash? Disabling optimisation for exec_recompiler() will absolutely kill performance, it's the dispatcher for the recompiler and definitely needs to be optimised! It only happened on release builds, it was beyond odd. But it could have been due to missing optim...

Found the build: https://github.com/sarah-walker-pcem/pcem/commit/bc59a414b51bc20f27989e87e8044866afa76031 So I did a Release build with that optimization disable attribute removed, if possible can you check to see if this build has the same lag issues? https://repo.nasutek.com/repository/pcem/pcem/...

Going back I did notice this

https://github.com/sarah-walker-pcem/pcem/issues/92

It seems one function got optimizations disabled due to the emulator crashing, I need to find which build I implemented this in. Could be GCC is optimizing wrong.

I'll look into what changed since v17 and now. I have yet to do any code changes on Dynarec so it's very strange it has any slowdown in that area.

Humm, you shouldn't even be asked for PCap if Networking is off. I'll push a fix for that now.

Should be able to compile now if you pull recent code

@unreal9010: Can you test and see if build 85e1ef3 is better in regards to speed https://github.com/sarah-walker-pcem/pcem/actions/runs/2056679721 This build now uses compiler flags more on par with v17's release. GitHub Action builds were built with optimizations, so it was odd the speed difference...